March 30, 2012 at 11:11 am
sqlfriends (3/30/2012)
Thank you, sorry it is kind of hard to understand the memory configuration.But from what paul.knibbs said to set to max 2.5 GB, but opc.three said to set it to 1.6 GB,
I am a little confusing.
We plan to migrate this server in June for 64 bits 8 GB.
But for now we have to live with it, I just wonder if I change the server max memory will help or not.
Also if that's OK not to reboot the server after changing the memory setting?
The server hosts an important application and runs both db engine and ssis on it.
Setting the max memory to 2.5GB will do nothing at the moment, since the most RAM SQL Server can theoretically access for the buffer pool is 2GB, under your current configuration. We can see though that in practice SQL Server can only grab ~1.6GB.
Adding the 3GB switch will make it theoretically possible for SQL Server to access 3GB of RAM, but in practice the number the buffer pool will grow to is closer to 2.5GB.
I recommended setting max memory to 1.6GB so that when you add the 3GB switch SQL Server will continue to use the same amount of memory it currently uses for the buffer pool, leaving the additional 1GB completely there for the taking for SSIS, and other applications to use.
There are no special teachers of virtue, because virtue is taught by the whole community.
--Plato
March 30, 2012 at 11:15 am
sqlfriends (3/30/2012)
Also if that's OK not to reboot the server after changing the memory setting?
To answer this too, yes, you can change the max memory without rebooting. However, a reboot is necessary to get the 3GB switch change to take effect, which is why it is there as step 4.
There are no special teachers of virtue, because virtue is taught by the whole community.
--Plato
Viewing 2 posts - 16 through 16 (of 16 total)
You must be logged in to reply to this topic. Login to reply