July 30, 2008 at 1:12 am
What do you mean by 'memory consumption issues'?
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 30, 2008 at 5:31 pm
By memory consumption i mean every time i am getting alerts that SQL SERVER IS CONSUMING 100% OS MEMORY..Very frequently i am getting such alerts.
July 31, 2008 at 1:57 am
You may want to set the max memory lower. Maybe 3 GB. SQL's been told that it may use up to 3.5 GB and it will do that, even if it means starving the OS.
Just a check, 32 bit, 64 bit? Is /3GB enabled? Is AWE enabled?
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
August 1, 2008 at 8:44 am
If you aren't using Enterprise Edition, set sql server max memory to 2GB and see how that goes. If still get alerts, go with 1.7GB. If using EE, start with 2.5 and go down to 2 if problems. Check for paging using perf mon. If getting that during steady state ops, keep backing down until it goes away. Note that you may need to bounce sql server to get it to release memory.
What else is running on this server?
Like Gail said, if 32 bit (and EE) you will need /PAE and AWE enabled to use more than 2GB.
Best,
Kevin G. Boles
SQL Server Consultant
SQL MVP 2007-2012
TheSQLGuru on googles mail service
Viewing 4 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply