February 8, 2010 at 3:39 am
Hi, im pretty new to replication and trying to recover after a problem.
Over the weekend replication between our 2 servers had failed with a general network error. the message informed me that i would need to set up replication again as the subscription had expired.
To get around this, I updated the subscriptions table and set the status column back to 2. I restarted the agent now replicationis working again for new transactions, but i am left with a table of undisributed commands.
Is there a sproc that i can execute to apply the undisributed commands?
Thanks
February 10, 2010 at 2:03 pm
Just curious, what type of replication is this? And how long was replication down for? Because I know with merge replication if you experience replication with a subscriber go down you can usually restart the merge agent and everything that was in the queue at the distributor is then replicated.
That being said, you have a few options for finding/fixing the mismatches in the replicated databases. Some third-party companies offer tools to compare databases and fix the discrepancies. I believe RegGate who sponsors this site has one. Another alternative is to get the tablediff utility from SQL Server 2005. It can work against SQL 2000 databases and can also show you discrepencies. It can even make a table with the differences as well as generate scripts you can run to fix the mismatches. Just ensure you pour over them to make sure it is doing what you want before you run it.
Here is the SQL 2005 BOL article on tablediff:
Joie Andrew
"Since 1982"
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply