long running queries quit - audit logout
From: Gary (gld_at_hotmail.com)
Date: 08/11/04
- Next message: Keith Kratochvil: "Re: detaching db and stopping services"
- Previous message: Keith Kratochvil: "Re: restore problem"
- Next in thread: oj: "Re: long running queries quit - audit logout"
- Reply: oj: "Re: long running queries quit - audit logout"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 11 Aug 2004 17:01:59 GMT
I have a web based application that launches sql queries using ADO from
ASP/VBScript. Typically 2 - 10 queries are executed in a loop, and the
result sets are sent off to Crystal Reports at the end of the run with the
report being displayed in a browser window. In general this all works well
is has been very reliable.
Lately I've been having trouble with some of these queries on databases that
have gotten quite large (25 - 40G) but only a couple of the tables have
rowcounts in the tens of millions, most are relatively small. The behavior
is that the first query runs, sometimes for up to 90 minutes, seems to
complete, and then the pid is gone. Looking at the profile trace, I can see
that the query executed nearly 13 M reads with a duration of over 90
minutes. The line following the SQL:BatchCompleted event is Audit Logout,
and thats the last trace of the process. Under "normal" operation, the next
query would start and they would all run until the loop is complete. I've
seen this now with 2 completely different sets of queries, on 2 different
dbs, yet the symptoms are the same. It completes a very simple query that
returns a single datetime value. Then the first "real" query runs, anywhere
from 60 - 90 minutes or more, and then the process goes away.
It seems as if I've reached some threshold or internal timeout. I have the
connection time and query timeouts set to very large values (1000 minutes),
so it's not that.The client process is of course IIS. This is running SQL
Server 2000 SP3, NT 4.0, IIS 5.5.
I have had sets of queries that have taken as long as 3 hours to complete,
but each individual query probably never exceeded 45 minutes in duration.
Can anyone think of what is causing this to happen -- why does the pid go
away after the first query completes? Is there some other internal timeout
somewhere that I'm running into?
Any advice is appreciated,
-Gary
- Next message: Keith Kratochvil: "Re: detaching db and stopping services"
- Previous message: Keith Kratochvil: "Re: restore problem"
- Next in thread: oj: "Re: long running queries quit - audit logout"
- Reply: oj: "Re: long running queries quit - audit logout"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|