In the production server we are noticing blocks & dead-locks. I have used trace flag 1204 to capture info for deadlock which hapens very rarely.
I am seeing blocks every now & then. Is there any tools/system tables to query to get more info abt blocking & blocked spids. I used info from syslockinfo & sysprocess. dbcc inputbuffer gives info like 'sp_cursorunprepare;1' or 'sp_cursorfetch;1' and puts exclusive locks on bunch of tables. However no activity is seen for that spid.
Any help will be appreciated. I am using SQL Server 2000 with SP2
RachaelTry with sp_who2 and adding (NOLOCK) in your selects.
Csar.
Showing posts with label noticing. Show all posts
Showing posts with label noticing. Show all posts
Monday, March 19, 2012
Thursday, March 8, 2012
Blocking in distribution database...
Hello...
I am noticing that everytime the the Agent history clean
up job runs... it causes contention and blocking in the
distribution database.
Has anyone come across this? If so, how did you resolve
this. I am using SQL Server 2000 and every server in my
topology uses SQL Server 2000 as well.
Please advise...
Thanks,
Brett
are you running datamirror? Datamirror does not clean up efficiently.
Blocking in the distribution database is caused by 2 factors
1) too many push agents running simultaneously. Try to stagger and schedule
them. If you can migrate to pull subscriptions.
2) too much replication metadata pooling in your distribution database due
to subscribers who are frequently off line. If you are using anonymous
subscribers this exacerbates the problem. Consider using named subscribers.
"Brett" <anonymous@.discussions.microsoft.com> wrote in message
news:1ae2001c41e7a$fc3ac590$a101280a@.phx.gbl...
> Hello...
> I am noticing that everytime the the Agent history clean
> up job runs... it causes contention and blocking in the
> distribution database.
> Has anyone come across this? If so, how did you resolve
> this. I am using SQL Server 2000 and every server in my
> topology uses SQL Server 2000 as well.
> Please advise...
> Thanks,
> Brett
>
I am noticing that everytime the the Agent history clean
up job runs... it causes contention and blocking in the
distribution database.
Has anyone come across this? If so, how did you resolve
this. I am using SQL Server 2000 and every server in my
topology uses SQL Server 2000 as well.
Please advise...
Thanks,
Brett
are you running datamirror? Datamirror does not clean up efficiently.
Blocking in the distribution database is caused by 2 factors
1) too many push agents running simultaneously. Try to stagger and schedule
them. If you can migrate to pull subscriptions.
2) too much replication metadata pooling in your distribution database due
to subscribers who are frequently off line. If you are using anonymous
subscribers this exacerbates the problem. Consider using named subscribers.
"Brett" <anonymous@.discussions.microsoft.com> wrote in message
news:1ae2001c41e7a$fc3ac590$a101280a@.phx.gbl...
> Hello...
> I am noticing that everytime the the Agent history clean
> up job runs... it causes contention and blocking in the
> distribution database.
> Has anyone come across this? If so, how did you resolve
> this. I am using SQL Server 2000 and every server in my
> topology uses SQL Server 2000 as well.
> Please advise...
> Thanks,
> Brett
>
Subscribe to:
Posts (Atom)