October 5, 2005 at 8:29 am
Unaccountable, our new windows 2003 server with sql server seemingly at random intervals is freezing. This is a closed system not on the internet that we are developing our app for and the freezup occurs even when the client workstations are not being used. The symptom is that about 3 - 4 times an hour the server disk queue length hits 100% and remains there for about 90 seconds. During that time it is difficult to even click on the "start" button and get a response. If running, for example, sqlmanager, pressing F1 for help might take 20 - 30 seconds before the outline of the dialog box appears. This can happen with "no load" on the server. Something is set up wrong or there is a hardware problem??? Usually this happens a couple of times a day but sometimes it is 3-4 times an hour.
How do I get a handle on what is going on? If we are running an app, for example, updating just 10 records in the database, our sql connection on the client will time out after 30 seconds if we attempt to make the connection while the server is displaying that 100% disk quota length. It used to be worse when we had raid 3. We migrated the os & server stuff over to a single IDE drive (ie: got rid of the raid) and things improved to where it was only about 90 seconds instead of 3 minutes or so of "freezup" time.
Can too much security loging cause this? I think anything that can be logged was enabled by our security officer for that 2003 server.
October 5, 2005 at 1:35 pm
1)Is there any application active on the server except Windows 2003 and sql server? (Antivirus, IIS,...)
2) Ms full search is enabled?
Viewing 2 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply