June 23, 2003 at 8:05 am
Hi,
We had some problems with our production server today. Seems like transactions between 12:00 pm - 3:00 pm were not replicated. Probably due to some errors on the distribution. We manage to fix that problem now but how to do Sync the amount of data between the production Database to the reporting database without having to recreate the schema and initializing the data again. I have some tables which are 88 million rows and 77 million rows in total which will take along time.
If there is a method or suggestion would gladly appreciate to listen.
Thanks
June 23, 2003 at 10:48 am
The only alternative that comes to my mind is to update all the rows that got missed and then replication will replicate them. Of course if there are too many missed rows then that won't be a good alternative.
Robert W. Marda
SQL Programmer
bigdough.com
The world’s leading capital markets contact database and software platform.
Robert W. Marda
Billing and OSS Specialist - SQL Programmer
MCL Systems
June 23, 2003 at 10:48 am
If you can identify the rows, you could manually do the inserts/deletes to the subscriber, then update all affected rows on the subscriber to let the changes propagate. Are you sure the transactions aren't still queued in distribution?
Andy
June 23, 2003 at 1:49 pm
Check first if the log reader manage to move the transactions to the dist db.
You can use sp_browsereplcmds in the dist db to see all the transactions that are waiting to be distributed.
I would also disable the clean up jobs, until I can certified that the transactions are not in the distribution db.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply