URGENT!!! Locking timouts
From: Peter The Spate (anonymous_at_discussions.microsoft.com)
Date: 10/01/04
- Next message: bnhcomputing: "Check Constraint isse"
- Previous message: dwaine: "creating jobs programmatically causes deadlocks"
- In reply to: ChrisR: "URGENT!!! Locking timouts"
- Messages sorted by: [ date ] [ thread ]
Date: Fri, 1 Oct 2004 09:16:34 -0700
You can use the profiler but modify it to look at queries
that say take more than 5 seconds.
In the meanwhile try changing your timeout in SQL Server
to 0, which means it will never time out.
If your doing it though ADO then do the same with your
connection object.
Other than that, not really.
"Government does not solve problems; it subsidizes them."
Ronald Reagan
>-----Original Message-----
>sql2k sp3
>
>
>An application is kicking out an generic error message
>saying that the execution of an sp is taking too long and
>causing a timeout. To add to the problem, its happening
>very inconsistantly. I would be the first to say that it
>may not really be SQL's fault, but I still need to
>research. Aside from running profiler forever waiting for
>it to happen again, is there anything else I can do to
>track down the problem?
>
>
>TIA, ChrisR
>.
>
- Next message: bnhcomputing: "Check Constraint isse"
- Previous message: dwaine: "creating jobs programmatically causes deadlocks"
- In reply to: ChrisR: "URGENT!!! Locking timouts"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
