May 29, 2012 at 12:50 am
Hi All
On friday we moved our SQL2000 production database from an old Dell server running Windows Server 2003 (x86) to a new Dell server running Windows Server 2008 R2.
We have installed SQL 2000 onto the new server with SP4, all latest service packs and updates have been applied as well to Windows.
The system is now suffering from timeouts regularly, it used to occasionally timeout but now its all the time? Has anyone got any ideas why it would suddenly get worse when we move a database from one SQL2000 server to another? the only significant difference is the hardware, as the new server is a lot more powerful and has 16Gb Ram where as the old server only had 4Gb.
I'd be grateful for any ideas or advice?
Thank You
Daf
May 30, 2012 at 2:38 am
Shot in the dark here, but have you ensured you've got AWE enabled and the PAE switch on? I think at default SS2K only addresses 2gb of memory, and if the box is already pretty busy it could be worth checking out. Again, just a theory to start you googling, couple of MVP's on here who can likely tell you more if you want to wait.
May 30, 2012 at 2:41 am
PAE is on, but AWE, thats a good question, I should check that! I will have a look and see if thats enabled and working. I did wonder if it was something to do with memory, specially with the way it was behaving. Thank you and I will get googling that 🙂
May 30, 2012 at 2:47 am
SQL 2000 is not supported on Vista, Windows 7, Server 2008 or Server 2008 R2.
Have you identified where the timeouts are occuring from? Is it logging in? Is it a specific query?
Firstly I would revert the OS back to Server 2003 if you want to stay on SQL 2000 or upgrade to SQL 2005/2008/2008R2.
If its query performance they might be a whole host of things you need to try, index maintenance, statistic updates for example.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply