Hi,
we have a merge replication SQL Server 200 solution that worked fine so far;
2 days ago we put a new table in replication and something new, that we
didn't see before happened: for some reason not all the records where bcp in
the new table for one of the subscriptions and there is a sp_upd ...
(strange name after upd) that runs every 1 minute and 4 seconds.
Any ideas?
Thank you so much!
use the conflict viewer to determine if there were any conflicts which might
account for the missing rows. Also the sp_upd statement means that there
are changes on the publisher which are being performed on the subscriber.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Sorin" <Sorin@.discussions.microsoft.com> wrote in message
news:5674968D-EE90-4348-8705-83BA8659ED75@.microsoft.com...
> Hi,
> we have a merge replication SQL Server 200 solution that worked fine so
far;
> 2 days ago we put a new table in replication and something new, that we
> didn't see before happened: for some reason not all the records where bcp
in
> the new table for one of the subscriptions and there is a sp_upd ...
> (strange name after upd) that runs every 1 minute and 4 seconds.
> Any ideas?
> Thank you so much!
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment