December 10, 2007 at 5:41 pm
My organization is currently migrating about 35 databases from SQL 2000 to SQL 2005. WE are about half way through as we started
the project a year ago. We purchased new hardware for this SQL 2005 so it is a side-by-side migration and it has been going well
so far. I made one oversight which I think will come back to haunt us down the line. I installed Windows Server 2003 Standard R2 Edition
and of course now I am considering putting more RAM in the server. We have 4 GB of RAM in the server and of course Standard Edition will not
address more 4GB of physical ram. I have not seen any memory pressure yet but as databases are migrated over the amount of physical
RAM drops. My buffer hit cahce ratio and page life expectancy performance counters are fine so far. The server is a brand new
HP DL 380 G5 with with tons of disk and processing power, but only 4GB of RAM. I can't migrate to another server with more ram obviously.
1. What would you do in a situation like this?
2. I could do an in-place upgrade to Windows Server 2003 Enterprise R2. Has anyone attempted and in-place upgrade? I have no applications
on this server, just SQL 2005 Standard.
3. Would the /3gb switch be an option? I have heard mixed reviews on this one.
As far as database optimization, %75 of the databases are third party so we have little flexibility in tuning them or redesigning
tables.
Thanks,
Alex
December 10, 2007 at 11:32 pm
Please don't cross post. Continued here
http://www.sqlservercentral.com/Forums/Topic431592-149-1.aspx
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply