Replication Troubleshooting Tips

[Valerie]

Hi all:

I'm new to replication but I have already set up replication and have seen it
working and failing and have gotten myself out of jams so far but there must
be an easy way to administer it when things don't replicate as expected. I'm
finding that I could easily kill half a day just trying to dig up
information leading to troubleshooting tips. Is there documentation just on
managing this feature. The regular MS Administrator's guide doesn't offer much.


Currently I have a problem that if replication fails on one command I get a
SQL Mail telling me of the problem but does replication continue to the next
command or does it just stop until the problem is fixed? I'm finding that I am
constantly checking the publisher and subscriber databases and verifying if
replication is indeed doing what the msjob_commands table reports. I set the
batch to commit after each transaction instead of every 100.

Help...

[Patrick]

Hi Valerie,

About the commands stored in the MsJob_Commands table of the distribution base, if one command for one server doesn't work, the replication for this server is blocked, However the commands for the other subscribers continue to work.
The purge of MsJob_Commands is done by day at 1 AM by a sceduled task. The commands not worked remains in the table. However in the working hours if you want to look at the commands contained in this table, you could start/run the "Cleanup" procedure. Be careful this proc generate a lot of lock situation.
It is necessary to find why the command is rejected by the subscriber (Constraints like DupKey. Foreign K.)
Remember that while the server is still subscribing the publication, the commands stay in the MsJob_Commands. that could impact the size of the distribution database if it get new commands each day/hour. The good new is that when the problem is solved, all the commands go to the subscriber. Think to help the distribution task to start.

If you need more precise help, don't hesitate to contact.

Bye
On 1/6/99 1:24:49 PM, Valerie wrote:
> Hi all:

I'm new to replication but I have already set up replication
> and have seen it
working and failing and have gotten myself out of jams so
> far but there must
be an easy way to administer it when things don't
> replicate as expected. I'm
finding that I could easily kill half a
> day just trying to dig up
information leading to troubleshooting tips.
> Is there documentation just on
managing this feature. The regular MS
> Administrator's guide doesn't offer much.


Currently I have a
> problem that if replication fails on one command I get a
SQL Mail telling
> me of the problem but does replication continue to the next
command or
> does it just stop until the problem is fixed? I'm finding that I
> am
constantly checking the publisher and subscriber databases and
> verifying if
replication is indeed doing what the msjob_commands table
> reports. I set the
batch to commit after each transaction instead of every
> 100.

Help...