Posted - 10/27/2012 : 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.
I 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.
Is to stop the system that uses the online database then
1- Take a full backup.
2- Remove old replication configurations for that database (Publisher and the distributor and the subscriber)
3- Restore database
4- Rebuild The replication
5- 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.