We have updated to SQL Server 2005, let’s say, in a hurry without thinking or testing. Databases were attached to the new instance of SQL Server 2005. It looked great when I tested it alone but then a new day come and as all users logged into the system we had got a big problem. The response times are very long and users receive time out errors all the time.
A little background:
The instance of SQL Server 2005 is installed on the same server as 2000 was installed on. 2000 has been uninstalled. It is a Xenon 3.2 GHz with 2GB RAM and SCSI raid. Data and logs are on different spins.
Application is an old ASP code and some parts are not optimized at all. But it worked fine on SQL Server 2000.
What could be the problem?
I really don’t want to downgrade to SQL Server 2000.
Hi Stolin,
Just wondering if you ran UPDATE STATS after the upgrade.
If not, This is the first thing I would do. UPDATE STATS with FULL SCAN.
Good luck and let us know how u get on
Jag
|||Thank You,
That’s exactly what I did right after I’d posted the message. I also rebuild the indexes. Let’s hope that’s enough.
No comments:
Post a Comment