Steps to find out / Resolve SQL Server High RAM usage in SQL Server 2008.

Question

Post reply

Steps to find out / Resolve SQL Server High RAM usage in SQL Server 2008.

rajasekar.x.jeyarajan

SSC Veteran

Points: 273
More actions
June 5, 2012 at 4:19 am

#259112

Hi all,

I have SQL Server 2008 and its handling around 10 Million transactions, and the server is always running with high memory usage ( RAM ). Need to know the steps to findout / resolve this.

Viewing 7 posts - 1 through 6 (of 6 total)

You must be logged in to reply to this topic. Login to reply

spaghettidba SSC Guru Points: 105712 More actions · Answer 1

spaghettidba

SSC Guru

Points: 105712

June 5, 2012 at 4:45 am

#1496963

High memory usage is not a symptom of memory bottleneck per se.

Did you set MAX SERVER MEMORY?

Did you monitor PAGE LIFE EXPECTANCY?

See this blog[/url] for more information.

-- Gianluca Sartori

Gail Shaw SSC Guru Points: 1004494 More actions · Answer 2

High memory usage is typically what you want, it means SQL is using the resources on the server.

Chapter 4: http://www.simple-talk.com/books/sql-books/troubleshooting-sql-server-a-guide-for-the-accidental-dba/

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

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

rajasekar.x.jeyarajan SSC Veteran Points: 273 More actions · Answer 3

Page Life Expectancy :

Buffer Manager Page life expectancy 7414 65792

Buffer Node Page life expectancy 8077 65792

Buffer Node Page life expectancy 6851 65792

Max Server Memory is : 9 GB

Total Server mem : 12 GB.

pls help on the steps to be taken to reduce high mem. struck with this . 🙂

Gail Shaw SSC Guru Points: 1004494 More actions · Answer 4

Once again...

High memory usage is typically what you want, it means SQL is using the resources on the server.

Those values look good, I'd love a server with such high page life.

Chapter 4: http://www.simple-talk.com/books/sql-books/troubleshooting-sql-server-a-guide-for-the-accidental-dba/

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

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

derek.colley SSCrazy Eights Points: 8040 More actions · Answer 5

OP, please could you actually read the replies to your original post, high memory use with SQL Server is not a problem most of the time, if you want to reduce the memory consumption then cap the memory use as described and restart the SQL Server service. Beware if you're doing this since you need to correlate the demand on SQL Server with the actual memory requirement and reduce the excess accordingly.

Please also read the links posted for you about diagnosing problems with memory use, better DBAs than you have spent hours researching and writing about these issues, a one-line magic answer is not something you'll get when you're talking about performance. Glenn Berry's article linked above is a good place to start, also see the Brent Ozar training videos http://www.brentozar.com/sql-server-training-videos.

EDIT: Having a bad Friday... :crazy:

---

Note to developers:
CAST(SUBSTRING(CAST(FLOOR(NULLIF(ISNULL(COALESCE(1,NULL),NULL),NULL)) AS CHAR(1)),1,1) AS INT) == 1
So why complicate your code AND MAKE MY JOB HARDER??!:crazy:

Want to get the best help? Click here https://www.sqlservercentral.com/articles/forum-etiquette-how-to-post-datacode-on-a-forum-to-get-the-best-help (Jeff Moden)
My blog: http://uksqldba.blogspot.com
Visit http://www.DerekColley.co.uk to find out more about me.

derek.colley SSCrazy Eights Points: 8040 More actions · Answer 6

Another link for you using a different method from Grant Fritchley:

http://blogs.msdn.com/b/mvpawardprogram/archive/2012/06/04/using-sys-dm-os-ring-buffers-to-diagnose-memory-issues-in-sql-server.aspx

---

Note to developers:
CAST(SUBSTRING(CAST(FLOOR(NULLIF(ISNULL(COALESCE(1,NULL),NULL),NULL)) AS CHAR(1)),1,1) AS INT) == 1
So why complicate your code AND MAKE MY JOB HARDER??!:crazy:

Want to get the best help? Click here https://www.sqlservercentral.com/articles/forum-etiquette-how-to-post-datacode-on-a-forum-to-get-the-best-help (Jeff Moden)
My blog: http://uksqldba.blogspot.com
Visit http://www.DerekColley.co.uk to find out more about me.