Help! I've killed a client! Merge Replication
-
Desktop program was calling repeatedly and needlessly a stored procedure that was locking a table, deleting a brazillion rows and adding them back. Correction was sent, but silly users wouldn't stop using the mad program and locking this frequently used table for minutes and on and on... Of course, this happens to be the client with high bloodpressure and he's storming the gate.
So I deleted the offending stored procedure at the subscribers to put a stop to this endless locking, deleting, reinserting.
When I went to delete it from the publisher, it objected most strenuously. So I modified it to do nothing. (This procedure is supposed to be used once in a blue moon)
But when replication attempted to alter the procedure that has been deleted, all came to a stop. I can't find any evidence that it's going by inserting a row and looking at another database to see if it's arrived.
The sync monitor says
If I hit the start button, it says it can't 'cause it's already started.
So, how do I get this mess going again?
I have a window of several hours tomorrow when the users won't be around. I do need to get the data replicated from the subscribers to the publisher before I kill and rebuild things.
[font="Arial"]Halfbubble ------------
You just can't do this stuff unless you're at least half a bubble off center.[/font] -
Oh my! I got it solved....
I recreated the deleted procedure at each of the subscribers so the alter statement would work. Now the replicator is again replicating.
[font="Arial"]Halfbubble ------------
You just can't do this stuff unless you're at least half a bubble off center.[/font] -
Beneath 4 million rows in the customer lookup table. (Shhh)
[font="Arial"]Halfbubble ------------
You just can't do this stuff unless you're at least half a bubble off center.[/font]
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply