February 26, 2003 at 10:06 am
I have recently set up the Replication Agents Checkup job to notify me upon failure on several servers. I have one server where the job fails a few times a day. When I look in the job history, it tells me that there was a deadlock, but not much more. How can I find out what keeps causing this deadlock, which database it is occurring in or more about what this job is actually checking?
February 26, 2003 at 10:25 am
Treat it like any other deadlock. Start by enabling trace flag 1204/1205. Once you get the results of a deadlock or two in the log, then you can start to narrow things down. It's the distribution agent that is failing? If so usually due to contention in the distribution db, fix is to make sure not so many agents run at once, decrease batch size, or look at putting distribution db on another server.
Andy
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply