February 21, 2012 at 4:15 pm
We will be moving a database from SQL 2000 to SQL 2005. SQL 2005 server already has a huge database and this server has 8 processors and 64GB physical memory. SQL 2005 server is mostly busy during 9am-1Pm weekdays. I'd like to know if I could give specifics to manager regarding the impact on the 2005 server if sql 2000 database is moved.
SQL 2000 server processor count is 16 and physical memory is 64GB.
February 22, 2012 at 4:18 am
You need to gather metrics on the 2000 server and then pass those on. The code and structure are not going to change by migrating from 2000 to 2005. That means if you have 1000 transactions/minute in 2000, you'll have 1000 in 2005. If you have 500gb log files in 2000, you'll have 500gb log files in 2005. Just gather the metrics and pass them over.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
February 22, 2012 at 4:31 am
February 22, 2012 at 7:37 am
In addition to the previous comments, I also advise running PerfMon on the 2005 server to see if the hardware is at capacity or not.
If you're starting to see memory leaks, full CPU usage, or IO problems, adding another database to the server is probably a bad idea.
Run PerfMon periodically during the busy hours (snapshot the numbers) and during the slow times to get a better idea of how your system is handling things.
And doing a server-side Profiler trace at the same time would be a good idea too. That way you can see the effect the SQL transactions are having on your system.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply