November 29, 2004 at 8:29 am
My replication works fine every day, until I come back the following week on Monday and the replication is completely locking up the server that is running as the distributor (the distributor and subscriber are separate computers). I used sp_who to find what is causing the problem, and the distribution is blocked and locking up everything. When I shut all publications down, and turn on the log reader the CPU Usage hits above 80%, and it stays at that. During the week it works fine, but something on the weekend is causing it to lock up and never return to working condition. The only way to fix it is to completely delete and recreate the replication. Does anyone have any ideas what could cause the replication to lock up this way, to where it is completely hogging all of the cpu usage?
**There are no weekend programs or sql jobs that have been added that would cause this.
I am having horrible trouble with this. This is my second post on this, and I apologize for that, but this problem won't go away.
Thanks for the help.....Adam
November 30, 2004 at 3:43 pm
November 30, 2004 at 3:51 pm
A. Not sure if this is what you want for the model but, the replication is 14 articles (all tables are indexed, most are clustered indexes). There are 17 subscribers. Distributor and Publisher are separate servers.
B. The replication is transactional, and it needs to be transactional because the subscribers need up to date information for application purposes
C. I have not set up a profiler trace. How do I set one up and use it?
Thanks, Adam
Viewing 3 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply