Sometimes SQL Server slow in the morning - w2003 + sql 2000

I recently upgrade a server to run w2003. It was a clean install that had been happily running w2000 with the same database application backend on for years.

Since the upgrade, on two occassions I've come in, in the morning, to find the database application is running like a pig  ... it still works as it should but results are taking 10 times longer than normal to return.

A 'restart' of the MSSQLSERVER service sorts it instantly, although obviously that is less than idea as it kills the application which people are using.

Does anyone have any ideas why this might be happening ... it never happened until w2000.

Using SQL 2000 + SP3. I am pretty useless as using any tracing/debigging tools in SQL, so if you are going to suggest anything like that, go easy on me ....

Many thanks

Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

If this is happening on an occasional basis, it is likely that there is a user/app running a process that is taking a lot of resources on the system.

Next time before you restart the service and stop everything that is running, have a look within Enterprise manager, Expand the Mmgt tab,  Current Activity, and have a look to see if anybody is blocking anybody else or what is actually running on the server.  You can check the three wait type fields to determine who/what is part of the cause of the bottleneck.

You can also run: sp_who -- to find out what is running on the server in QA.
If all this fails, setup a sql-server profiler trace to capture the user commands that have been run onto your server so you can then examine them later. (If you don't know how to use this have a look on MSDN -- Microsoft, lots of instructions there).

Another way is to buy a product such as lumigent log explorer which will let you see what was running in the transaction logs, so when you restart the machine you can examine the transaction log to determine what was making the whole thing go wrong.  Okay you have to buy this product but it is very easy to use and useful.

I doubt that it has anything to do with running on w2003, that the server is running slowly -- it is recommended not to upgrade a w2000 machine to w2003 and do a clean install.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
"Sometimes SQL Server slow in the morning "   Kinda like me :)

It wouldnt be a scheduled full db backup or something would it.
SpencerSteelAuthor Commented:
Thanks guys- I'll let you know what I find ...

(Oh, I did do a clean install - sorry for any confusion)

It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SQL Server

From novice to tech pro — start learning today.