Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
AskSQLTeam
Ask SQLTeam Question
0 Posts |
Posted - 2004-06-02 : 07:20:06
|
| don conrad writes "I've a clustered SQL 7.0 on a NT 4.0 Enterprise edition. Several weeks ago, the server started hanging in a more or less random fashion. By hang, I mean all users connected would simultaneously freeze. This was/is true of those accessing via applications, via query analyzer, or enterprise manager. This is true for those remotely contacting the server as well as those accessing the console from PCAnywhere. Some processes could access via command line. Internal jobs appeared to continue without pause. EG I have a job which issues a date-stamp record every minute. That continues to function. The hangs last from 2-8 minutes, though the last two weeks most of the hangs only last 2-3 minutes. We've taken numerous PSSDIAG dumps. The only counter which seem to predict a hang was and increase from 0 to 40 or so of memory grants pending.During the hang, CPU utilization drops to near zero, disk queue length increases, and batch requests plumment. Rows processed per the profiler drops from 9000/sec to 3000/sec.It's as if work completed isn't being sent out, so no new requests are coming in.Sometimes this occurs once a day during full activity, sometimes at low activity. There seems to be no real pattern other than it happens more frequently during high activity than during low.When the hang completes all users are able to access the database, CPU spike high for a few minutes and then returns to normal. No data appears to be lostMS has found nothing so far from the various dumps and logs we've sent them. They appear somewhat mystified. Please contact me at Donald.conrad@Savvis.net314.580.0100Thanks in advance." |
|
|
Wanderer
Master Smack Fu Yak Hacker
1168 Posts |
Posted - 2004-06-02 : 07:50:56
|
| Any chance this is network related? You say that the various applications are affected - I am assuming that these all run from clients, across your network, yet you timestamp server, which I'm guessing runs locally, is ok?Have you tried to work local on the box during the "hang-periods" - say using QA local to run the same query that hangs from a client...*##* *##* *##* *##* Chaos, Disorder and Panic ... my work is done here! |
 |
|
|
|
|
|
|
|