Re: SQL Deadlock

Greg Dobinson ( (no email) )
Sun, 5 Jul 1998 19:44:33 -0500

Nothing else is using the SQL server for logging etc. However just today
we tried another consolidation and this time things seem to be
working......??? Nothing that I can think of has changed since we last
tried and failed. The only thing I can think of is that there were fewer
users on when we tried and succeeded than when it was failing.

Any thoughts?(Not that I need to solve a solved problem but it would be
interesting to figure out what happened)

Greg.

----------
> From: Dale E. Reed Jr. <daler@iea-software.com>
> To: emerald@iea-software.com
> Subject: Re: SQL Deadlock
> Date: Sunday, July 05, 1998 6:18 PM
>
> Greg Dobinson wrote:
> >
> > In my quest to get the consolidation process to work I have come across
> > this error message when doing a consolidation 12 in the ISQL_w utility.
> > SQL has detected a deadlock. Your connection has been chosen as the
> > deadlock victom.(not quite exactly of course).
> >
> > I understand that a deadlock happens when two processes have locks on
data
> > and each of the processes is waiting for the other to finish. How do I
> > make change it so the consolidation isn't picked as the deadlock
victom?
> >
> > I am running MS SQL Server 6.5 with SP4 on NT 4.0 SP3.
>
> AFAIK, you can't. I'd be curious as to what could be contending with
> it for a lock, though. What else is running?
>
> --
> Dale E. Reed Jr. (daler@iea-software.com)
> _________________________________________________________________
> IEA Software, Inc. | RadiusNT, Emerald, and NT FAQs
> Internet Solutions for Today | http://www.iea-software.com