November 4, 2006 at 4:31 am
How to avoid the self blocking in sql server it degrade the performance.
Please give me the ASAP reply
November 6, 2006 at 4:29 am
Question is too vague. If you're inferring parallel threads causing multiple spids which block the same user then search the forums , under parallelism, as it's been listed far too many times. If it's the user processes check out transaction isolation levels in BOL.
Buy Inside SQL Server 2000 or the admin companion from ms press
[font="Comic Sans MS"]The GrumpyOldDBA[/font]
www.grumpyolddba.co.uk
http://sqlblogcasts.com/blogs/grumpyolddba/
November 6, 2006 at 9:19 am
hi
Perhaps I am barking up the wrong tree here - but do you mean spids which sp_who2 suggest are blocking themselves? If so, this is just a change in the proc at sp4. Scared hell outta me before I realised that!
November 6, 2006 at 9:50 am
1. Run your scripts sequentially;
2. Make your scripts short.
November 7, 2006 at 9:07 am
don't know about sp_who2 , never use it, parallelism can cause blocking on same spid - check out cxpacket locks/waits.
I agree about sequential . short but not totally appropriate for a 1000 user oltp system.
[font="Comic Sans MS"]The GrumpyOldDBA[/font]
www.grumpyolddba.co.uk
http://sqlblogcasts.com/blogs/grumpyolddba/
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply