Re: Immediately after initializing a merge subscription, why would the subscriber send back updates?

Laurence,
one posibility is to mark the triggers as NOT FOR REPLICATION, which will
cause them not to fire as a result of records changed during the
synchronization process. As far checking what records are affected, I have a
script that might give you what you want
(http://www.replicationanswers.com/Script9.asp). It will list pending
changes and can't be used retrospectively, but might still be useful.
Rgds,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)


.

Relevant Pages

  • Re: merge publication
    ... setting up merge replication changes the structure of the database. ... It explains why the ROWGUID column and three triggers are needed. ... SQL Server will use that column automatically as the row ... has the ROWGUIDCOL property and an index, to the publishing table. ...
    (microsoft.public.sqlserver.replication)
  • Re: SPID question
    ... Transactional replication does not fire triggers. ... I am not sure if the context would be the same spid, ...
    (microsoft.public.sqlserver.replication)
  • Re: Merge Replication Problem
    ... you deselect the check box the triggers will fire. ... Paul Ibison SQL Server MVP, ... (recommended sql server 2000 replication book: ...
    (microsoft.public.sqlserver.replication)
  • Re: Replication problem.. Please help..
    ... new columns and/or triggers that has caused issues. ... If it is the GUID ... Paul Ibison SQL Server MVP, ... (recommended sql server 2000 replication book: ...
    (microsoft.public.sqlserver.replication)
  • Re: DTS Data not being Replicated
    ... If you do a fast-load using the Transform Data task in DTS the triggers ... won't fire. ... In merge replication you can run sp_addtabletocontents to get ...
    (microsoft.public.sqlserver.replication)
Loading