Re: Error: 16954, Severity: 10, State: 1 and Timeout problem


Thank's Erland!

Matik

Erland Sommarskog napisal(a):
Matik (marzec@xxxxxxxxxxxx) writes:
I have a SQL Server 2000 SP3 with one database.
On this DB are runing lot of threads from different applications. So
the access is multiple.

The problem is, on one of the applications (C++ programmed) I get from
time to time, problem, that the calls in database are sometimes
performed very very long.

If usualy it takes like 50ms, sometimes it takes up to over one minute!

I can not trace, why the application need so long time, to perform this
statement.
I've checked the code, but it seams to be ok.
Probably, other aplication are locking resources, so the first one need
to wait so long.

Question is, how to find out, which one is locking the resources, or
maybe which resources for so long?

I was trying to analyze SQL Profiler, but the only error I found was
this one:

Error: 16954, Severity: 10, State: 1

The text for this message is "Executing SQL directly; no cursor."

Help me, how to diagnose the problem. How can I trace, which processes
are blocking eachother.

You could try my aba_lockinfo. This stored procedure gives you a
snapshot of what is going on. Which processes that are active,
which are blocking and which are block. You get what they lock,
what they are waiting for, and their current statement. You find it on
http://www.sommarskog.se/sqlutil/aba_lockinfo.html.


--
Erland Sommarskog, SQL Server MVP, esquel@xxxxxxxxxxxxx

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx

.

Relevant Pages