Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
AskSQLTeam
Ask SQLTeam Question
0 Posts |
 Posted - 2006-05-02 : 08:16:03
|
| Paresh Joshi writes "Hi,I have setup a transactional replication on my Production Database and kept the authentication of the subscribers as Anonymous. Synchronization process works fine in most of the cases. But lately I am having a problems with few subscribers, whenever the synchronization process is terminated abnormally the second time the subscriber tries to sync it takes a lot of time and the process hangs up with the message Not Responding on the title bar. Even if it gets successful after about 8-9 hours, the transactions and commands that were synchronized are about 2 millions. I’m not sure how SQL is doing the roll-back or getting these transactions. Can somebody throw some light on the part how does the sync process work if the process was terminated abnormally in the previous attempt? Regards,Paresh Joshi" |
|
|
jen
Master Smack Fu Yak Hacker
4110 Posts |
Posted - 2006-05-02 : 21:19:56
|
| This is what I experienced,whenever a sync gets terminated, the entire batch gets rolled back, the rollback usually takes 2x or 3x the time for the commitSo make sure to drill down to the root cause for the interruption or you may need to schedule the sync during off peak hours instead of real time which actually beats the purpose if your intention is to relfect the changes as they are made on the publisher to the subscribersHTH--------------------keeping it simple... |
 |
|
|
|
|
|
Transactional replication Problem