Groups | Blog | Home
all groups > sql server replication > may 2007 >

sql server replication : some tables weren't replicated in replication


Iter
5/4/2007 9:23:01 PM
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
5/5/2007 12:00:00 AM
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
5/5/2007 8:50:00 AM
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.

[quoted text, click to view]
Iter
5/5/2007 11:08:01 AM
How can I re-synchronise it?

[quoted text, click to view]
Paul Ibison
5/7/2007 12:00:00 AM
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.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com



Paul Ibison
5/7/2007 12:00:00 AM
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...
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com



AddThis Social Bookmark Button