Replication out of step.
-
I have inherited a problem here which is coming back to haunt me every so often.
I have recently migrated two servers to SQL Server 2000 from Sybase 12.0 with transactional replication between them. I unfortunately did not set up the original servers and there appears to be some differences in the content of the tables at either end of the replication.
Is there a tool or a method to allow me to analyse the differences between each end so that I can attempt to analyse what I have to do to fix it.
I know I could do a snapshot but the major issue is with this is it would kill the subscriber as certain tables have some massive post replication processing done on them via triggers. So refreshing everything would basically kill the system for a week (I know I tried it on another system
)Thanks
Terry
-
Differences may occur and might be legal, if the subscribertables can be updated on the subscriver itself. I'm guessing from you posting this is not the case.
On comparing: with inner and outer joins you can find out what records are missing or superfluous in either table. With this info maybe you can decide which records in the subscriber to backup, then do a snapshot, restore the backed up records.
Ofcourse this will be difficult to impossible, if between the 'triggered' tables some kind of foreign key restrain is implemented.
If this would not work, you'll have to decide what's worse: shutting down the system for a week, to correct things, or to have differences between two replicated tables.
Greetz,
Hans Brouwer
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply