August 18, 2008 at 12:02 pm
Hello,
I'm trying to determine how much memory to give SQL2000. We're running Win2003 SP2 and SQL2000 Ent. with AWE enabled and have allocated 30GB to SQL.
Is this too much? Does Win2003 require more than 2GB? What allocation would be optimal?
--Thanks
August 18, 2008 at 1:00 pm
August 18, 2008 at 1:01 pm
Yes, 30GB is too much for SQL Server. I would recommend setting this to no more than 28GB and make sure the minimum is set to at least 1GB less than the maximum.
I have even seen recommendations to leave up to 6GB for the OS on systems with more than 16GB of memory. I haven't seen any issues with my system setup with 28GB max and 26GB min.
And finally, if you are running SSIS packages, reporting services, or any other services on this server you should decrease the maximum memory setting even further. This will all depend upon what resources the other services require.
Jeffrey Williams
“We are all faced with a series of great opportunities brilliantly disguised as impossible situations.”
― Charles R. Swindoll
How to post questions to get better answers faster
Managing Transaction Logs
August 19, 2008 at 9:08 am
Thanks for the info. We're backing it down to 28GB. Does this require a restart of the services?
August 19, 2008 at 10:32 am
Changing the memory settings does not require a restart. Just make sure you do not set the min server memory equal to the max (I recommend at least 1GB less than max).
Jeffrey Williams
“We are all faced with a series of great opportunities brilliantly disguised as impossible situations.”
― Charles R. Swindoll
How to post questions to get better answers faster
Managing Transaction Logs
August 23, 2008 at 11:37 am
It depends on how you change your memory setting.
If you use GUI, you do not need to do anything more, such as restart SQL.
If you change it using scripts, you need to run the RECONFIG WITH OVERRIDE after changing memory.
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply