October 10, 2003 at 4:41 am
Hi
I have some VB script that connects to a SQL database. Occaisionally, I get a:
[Microsoft][ODBC SQL Server Driver][SQL Server]Transaction (Process ID 57) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.
I'm pretty sure that the area of code that is generating this error is calling a stored proc that is simply selecting values from 2 tables into variables.
No other processes should be updating these tables, so no locks should exist, but there are many processes running the same select.
My question is, is it possible to get into a deadlock in this situation?
I can post the sp if neccessary.
Thanks
Andy
October 10, 2003 at 7:52 am
When u j=have multiple select statements querying the same subset of data there are chances that shared lock becomes deadlocked. I have experienced these issues before. And sometimes there might be someone with the table open at their end and this can also be a reason for deadlocks.
October 15, 2003 at 5:46 am
I would rewrite the queries or change db design. SQL Server cannot solve it. it is a problem of how you access your DB objects
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply