December 10, 2007 at 5:40 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 12, 2007 at 3:52 am
You most likely need to rebuild the operating system.
If all you have on the server is SQL 2005, you could install W2003 R2 Std 64-bit and SQL 2005 64-bit. This allows you to access 32 GB memory for no extra software cost.
If you need to stay on 23-bit, then you probably need to go to W2003 EE and use AWE memory in SQL.
Original author: https://github.com/SQL-FineBuild/Common/wiki/ 1-click install and best practice configuration of SQL Server 2019, 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005.
When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist - Archbishop Hélder Câmara
December 12, 2007 at 4:41 am
if server is purely for Sql server use of the /3GB switch will give you more headroom.
---------------------------------------------------------------------
December 12, 2007 at 9:22 am
Thanks. Can I use the /3gb switch with Server 2003 Stanard edition?
December 12, 2007 at 9:23 am
Have you ever done an in-place upgrade to Enterprise Edition. I have heard for the most part that it is pretty painless. I would rather not have to rebuild the server.
Thanks,
Alex
December 12, 2007 at 9:25 am
yep you can use with standard ed.
http://technet.microsoft.com/en-us/library/bb124810.aspx
---------------------------------------------------------------------
December 12, 2007 at 9:25 am
I know that the /3gb switch will leave the OS with 1GB of available memory. Do you know of any issues with this switch that would cause the server to have problems?
December 12, 2007 at 9:40 am
alex mook (12/12/2007)
I know that the /3gb switch will leave the OS with 1GB of available memory. Do you know of any issues with this switch that would cause the server to have problems?
never had any. as long as server has physical ram less than 16GB should be fine to use /3GB switch. You can always take it out if you get problems
---------------------------------------------------------------------
December 12, 2007 at 11:15 am
Thanks. I appreciate your help. I'm going to shoot for the /3b switch and try it out before I consider an in-place upgrade.
Alex
Viewing 9 posts - 1 through 9 (of 9 total)
You must be logged in to reply to this topic. Login to reply