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 ....