Thanks for your reply hmckillop.
The only thing is, the procedures I am running are part of a batch update job, which are run out of office hours at the moment and do not experience deadlocks.
Now I'm in the situation where I am going to have to run the batch update while users are logged on...
This may seem like a silly question, but it follows on from a question I had yesterday around deadlocks.
I'm doing a bit of research to find out the best way to avoid disastrous deadlocks on a batch update job that will be run daily while multiple users are accessing the database concurrently...
Thanks James - I think I'd be more inclined to address the error handling of error 1205 rather than SET DEADLOCK_PRIORITY. As it stands, I believe the current code should have minimal deadlock occurrences, but I want to implement something as a preventative measure going forward, to be on the...
Hi,
In the environment I am using, I need to run update scripts while users are logged into the SQL box. There is a possibility that they could be updating tables, causing a deadlock when I attempt to run my script.
As my update scripts are part of a daily job and of a definite priority over...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.