Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

some tables weren't replicated in replication

0 views
Skip to first unread message

Iter

unread,
May 5, 2007, 12:23:01 AM5/5/07
to
Hi Guy,
Today, I found some tables weren't replicated, they were not synchronised,
and some other tables got replicated. The replication setup is correct. I
checked the replication from replication monitor, no error, very strange. We
use transaction replication. Can anybody guess the reason? Is there any way
to check if the transactions were replicated? e.g. which system tables can I
check? Thanks.

Paul Ibison

unread,
May 5, 2007, 3:51:40 AM5/5/07
to
What do you see if you run sp_browsereplcmds or look at the view
MSdistribution_status?
Also, how were the tables added to the publication - if through script it
might be that they weren't added to the subscription (sp_addsubscription).
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com


Iter

unread,
May 5, 2007, 11:50:00 AM5/5/07
to
Thank you for reply. I checked the subscription, the table articles are
there. two days ago, they were fine. since then, no data were replicated. But
it is weird that not error occured. In subscriber, I have a job running every
5 minutes, and the duration of this job lasts 2 minutes. the job called a
stored procedure. I don't know if this job locks the table and make the data
lost or not. Is that possible to be happened? Thanks.

Iter

unread,
May 5, 2007, 2:08:01 PM5/5/07
to
How can I re-synchronise it?

Paul Ibison

unread,
May 7, 2007, 9:48:00 AM5/7/07
to
What about the first bit - "what do you see if you run sp_browsereplcmds or
look at the view
MSdistribution_status?". You could look at the posibility of blocking issues
but let's first confirm that there are commands waiting to be replicated.

Paul Ibison

unread,
May 7, 2007, 9:49:55 AM5/7/07
to
You can just right-click the subscription and mark for reinitialization, but
I'd investigate further instead - there's a good chance that
reinitialization isn't necessary. And besides, if you do reinitialize the
same problem may reoccur later so let's find out the root problem now while
we can...
0 new messages