July 10, 2008 at 3:27 pm
My SQL Server Ent 2005 64Bit Active / Passive Cluster is using 16.3GB of RAM and there is only 16GB in the server.
I have the max memory for SQL server set at 12GB but the process is running at 15.3GB ignoring the maximum settings.
Thus the server is swapping memory to disk. Lock pages in memory is enabled for sql service account.
How can i make sure the SQL server is limited in its memory usage if it is ignoring the setting.
Manu
July 11, 2008 at 12:24 am
How are you checking the memory used?
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
July 11, 2008 at 2:40 pm
Under task manager.
Manu
July 11, 2008 at 3:06 pm
Check what perfmon says.
Process:Working set (and select sqlservr.exe)
Also check the total and target server memory (I think that's under SQL Server memory manager. It's under one of the SQL objects)
I've never been happy with Task manager's memory readings.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
July 11, 2008 at 3:18 pm
in perfmon under Memory check "available bytes" too.
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
July 12, 2008 at 5:13 pm
Pretty sure that in 64 os the mem cons from task manager falls in the category of bogus.
July 12, 2008 at 7:21 pm
If you've got lock pages in memory on (which is the recommended setting for 64-bit), you can't rely on Task Manager or PerfMon. Neither properly report AWE memory, and with lock pages in memory on, even with 64-bit it'll be using AWE processes. You'll want to use DBCC MEMORYSTATUS.
More here:
How to use the DBCC MEMORYSTATUS command to monitor memory usage on SQL Server 2005
Slava Ok's Weblog - Q and A: Using Lock Pages In memory on 64 bit platform
K. Brian Kelley
@kbriankelley
July 12, 2008 at 9:13 pm
Good info by BRIAN.
Maninder
www.dbanation.com
July 14, 2008 at 8:48 am
Perhaps the max memory setting for sql server was changed AFTER the server had been running? I have seen sql server quite reticent to release memory back to the pool. May need to bounce it.
Also, what OTHER things are taking up memory on the server? Have you stopped unnecessary services?
Best,
Kevin G. Boles
SQL Server Consultant
SQL MVP 2007-2012
TheSQLGuru on googles mail service
Viewing 9 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply