October 12, 2010 at 7:38 am
Hi there, apologies if this has been covered before but I got bogged eye reading all previous posts.
We have a SQL 2005 server which runs happily at 2gb of memory utilization at startup, then as the users connect, over a period of a couple of hours the memory usage on the server builds up to just over 15gb. We have 16gb physically installed. Even in the small hours after most users are offline, the server continues to run at 15gb memory utilization.
Server specs are as follows:
Windows Server 2008 SP2
Quad Core processers
16gb memory
SQL 2005
At present we do not have AWE or any max memory commands in use. There are no other applications running on this server as it is purley for SQL database.
Is there any way I can check to see why the memory usage builds up. I know SQL grabs memory on startup and releases as required however as no other apps are running, is SQL hogging this memory?
October 12, 2010 at 8:08 am
Hi
You should set MAX Server memory to... :
a. 2 GB for Windows
b. xGB for SQL Server worker threads (http://www.coeo.com/presentations/Coeo_SQL_Memory.pdf)
c. 1GB for multi-page allocations, linked servers, and other consumers of memory outside the buffer pool
d. 1-3 GB for other application like backup program
physical server RAM - sum(a,b,c,d) = MAX Server Memory
You use 32 or 64 bit Operating System? 32/64 bit SQL?
Best regards,
Michał Marek
October 12, 2010 at 8:15 am
we use 64 bit operating system
I sort of knew we should use max memory but could not think of settings to use.
October 12, 2010 at 8:22 am
Hi,
AWE set only in 32 bit OS + "lock pages in memory".
Best regards,
Michal Marek
Best regards,
Michał Marek
October 12, 2010 at 8:37 am
Thank you for the quick replies. I will look into the max memory setting and hopefully this will resolve the issue.
Lee
October 12, 2010 at 8:42 am
To welcome 🙂
More about SQL Server Memory SET: http://www.coeo.com/presentations/Coeo_SQL_Memory.pdf
Best regards,
Michal Marek
Best regards,
Michał Marek
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply