October 12, 2006 at 11:53 am
Attempting to integrate stopping and starting replication with nightly reindexing script, so that we can prevent replication timeouts or deadlocks while running specific index tuning. While we attempted using the sp_stop_job command, it doesn't seem to do the trick. This should be similar to manually hitting start/stop synchronizing in the Replication Monitor.
Thanks
October 13, 2006 at 7:54 am
I am not sure that is all that manually hitting start/stop does.
Run a profiler with SP:Starting and RPC:Starting and you should be able to capture the chain of procedures called.
You may also want SP:Statement starting for deeper information.
You can then look at the system sprocs called to see what they do although they can be a bit tricky to read they are normally commented.
If you are lucky the start/stop will call a single sproc which may call others. In which case you would only need to call the same sproc.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply