Thanks Joe, I'm looking at your proposed method at the moment.
(In further digging I have come across custom resolvers using the
replrec.dll but seem to have hit a wall on that because theres so little
information about it, especially to develop for it in a .Net way. If anyone
has any experience good or bad.......)
"Joe Webb" <[email protected]> wrote in message
> Nigel -
> SQLNS provides a couple of functionalities that may do what you're
> First the built-in SQL Server Event Provider periodically checks a
> table to see if there have been any changes to the rows. (Yes, it's
> technically polling but you don't have to worry with the interval,
> etc, SQLNS handles it for you.) Using T-SQL you as the developer
> determine how those changes are to be recognized. The second way
> involves using some SQLNS provided procedures in a trigger for the
> data table.
> Either way, events are raised in the SQLNS application and subscribers
> can be notified via the built-in SMTP protocol or a custom protocol
> that you develop (i.e. a protocol that would communicate some
> Joe Webb
> SQL Server MVP
> Get up to speed quickly with SQLNS
> I support PASS, the Professional Association for SQL Server.
> On Tue, 31 May 2005 16:42:34 +0100, "Nigel"
> <[email protected]> wrote:
>>Thanks but I do not see how that meets the requirements as I *still*
>>have to poll tables (although they are now tables that I create rather
>>using system tables in the case of msmerge_contents which is a no no).
>>I did look at triggers but the problem is *how* to get the trigger to fire
>>an event on an application outside of SQL. I know the CLR support in
>>lets me use the SQLpipe to send data back upto the server, but how about
>>raising events on other applications??
>>(Note that I'm *not* interested in yuckky solutions with triggers writing
>>files/event logs with .Net doing file or event log watching).
>>"Hilary Cotter" <[email protected]> wrote in message
>>> You could modify the merge replication triggers to write to an audit
>>> table, or simple use new triggers which will write to an audit table.
>>> Another option is to query msmerge_contents and msmerge_tombstone.
>>> Hilary Cotter
>>> Looking for a SQL Server replication book?
>>> Looking for a FAQ on Indexing Services/SQL FTS
>>> "Nigel" <[email protected]> wrote in message
>>> news:[email protected]
>>>> What are the methods by which I can monitor replication/data row
>>>> I have looked at the Mergexlib but perhaps I've missed something but
>>>> *appears* to be for setting up and then monitoring (which is "ok"
>>>> how do I monitor previously configured subscribers? I cant see how I
>>>> set my mergeobj to an existing subscription as the DMO/MergeLib appear
>>>> be very different...). Will RMO in SQL2005 solve this and if so how?
>>>> Is there something I can do with the notifications services when rows
>>>> I'm looking at SQL2000 (and will be moving to SQL2005) and using the
>>>> environment and looking for an event based solution - I am not
>>>> in polling tables and running arcane sp's.