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 |
|
AnasTina
Starting Member
1 Post |
 Posted - 2012-10-27 : 12:14:56
|
| The replication of one my database stopped.The problem has begun when i tried to remove data from the online database (in the publisher server) but these deleted rows are not at replica database. So the problem is at subscriber side. First SolutionI have searched the internet and find that the logical solution is to let the subscriber continue its synchronization process even if he encounter error. This is done by change replication profile to skip errors. but the problem still exists. Now I have about 20 million undistributed command at the subscriber. Second SolutionIs to stop the system that uses the online database then1- Take a full backup.2- Remove old replication configurations for that database (Publisher and the distributor and the subscriber)3- Restore database4- Rebuild The replication5- Test the replication then run the system again.We are using Transaction Replication. What do you advise me to do with second solution. I am at planing stage. Is there minimum steps I can do .. minimum configuration.Thanks. |
|
|
namman
Constraint Violating Yak Guru
285 Posts |
Posted - 2012-10-29 : 12:58:14
|
| Did you reinitialize all subscriptions? That may fix your problems. |
 |
|
|
|
|
|
Replication Stoped !!.. suggested fix scenario