microsoft.public.sqlserver.server

Author

Deadlock on Tempdb

Shailesh Khanal

2002-11-08, 4:23 pm

Hi,

I have been posting a lot of message about deadlocks that
I am encountering, but it seems noone ran into similar
issues.

I have a new one now, I tried to run the same procedure
from two sessions and it got deadlocked on tempdb. The
procedure uses lots of temp tables. The deadlock occurred
on ncsysobjects index of sysobjects table.

The deadlock error log says both the sessions were running
line# 237, every time I have seen a line number it does
not translate to anything meaningful in my procedure. The
line 237 is in the middle of a select statement. This has
nothing to do with sysobjects table.

In earlier version (6.5), I had seen lots of blocking on
tempdb not a deadlock like this.

Any comments?

Thanks

Ricky Artigas

2002-11-09, 11:23 am

Using temp tables a lot could really result to deadlocks. Maybe you should
try to redesign your queries and minimize the use of tempdb.

"Shailesh Khanal" <skhanal@centresolutions.com> wrote in message
news:773601c2876f$e838a060$39e
f2ecf@TKMSFTNGXA08...
> Hi,
>
> I have been posting a lot of message about deadlocks that
> I am encountering, but it seems noone ran into similar
> issues.
>
> I have a new one now, I tried to run the same procedure
> from two sessions and it got deadlocked on tempdb. The
> procedure uses lots of temp tables. The deadlock occurred
> on ncsysobjects index of sysobjects table.
>
> The deadlock error log says both the sessions were running
> line# 237, every time I have seen a line number it does
> not translate to anything meaningful in my procedure. The
> line 237 is in the middle of a select statement. This has
> nothing to do with sysobjects table.
>
> In earlier version (6.5), I had seen lots of blocking on
> tempdb not a deadlock like this.
>
> Any comments?
>
> Thanks
>

Sponsored Links