March 4, 2004 at 7:03 am
Hi, I have one more question regarding SQL Server and its memory management. I know SQL Server is memory hungry and it will take as much memory provided to it and there is nothing wrong in it, but I am concerned with its sudden rush of memory consumption.
I have a dedicated SQL server which has 2 GB of ram, problem is whenever I restart (for any reason) SQL service, within 10 hours after its restart available memory comes down to only 500 Mb. This server also has Full text searching on and there are websites which use this facility. Now I want to whether this sudden rush of memory consumption is normal or is this a sign of something to happen? I will be fine if available memory be 200 Mb after a month of Uptime but not within couple of days.
Thanks
Saad
March 4, 2004 at 8:14 am
If you have allocated 2G of RAM for SQL Server to use, and are using dynamic it will use it as soon as it needs it. Most of this is data and procedure caching. This is by design and is expected, which is why you tell SQL Server how much RAM it can use.
When you start SQL Server it begins caching as it is being used. If you were to start it and not do anything with it, no interactive users and no scheduled job, it would not use the RAM. If you are using dynamic memory management SQL Server will eventually release some of the RAM if it is no longer needed.
With our production servers we have them set to use all of the RAM we have allocated for them at startup. One of my servers allocates 7.5G of RAM immediately when SQL Server starts.
Chris
March 4, 2004 at 10:54 am
The above explanation is pretty good. If you have concerns or performance issues, then you might try allocating a static amount of RAM to SQL Server, like 1GB or so and see if things run better.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply