March 19, 2018 at 7:11 am
I wanted opinions on the best way to determining how much memory a sql server instance is actually using versus what is allocated. We all know that SQL Server grabs all the memory that is allocated via Max Memory Settings or if Max Memory Settings is set to the default it will grab all of the memory, but, what I want to identify is what it's actually using. I have seen some threads on DMV's that can provide this information, but, I wanted a general consensus.
Thanks, in Advance.
March 19, 2018 at 8:04 am
I use this to measure SQL memory Usage and compare them with our baseline values.
Hari Mindi
http://www.dba-datascience.com
March 20, 2018 at 11:23 pm
This was removed by the editor as SPAM
March 21, 2018 at 8:54 am
ericwenger1 - Monday, March 19, 2018 7:11 AMWe all know that SQL Server grabs all the memory that is allocated via Max Memory Settings or if Max Memory Settings is set to the default it will grab all of the memory
No. It grabs memory as needed, up to max server memory. If it never needs that much, it won't allocate that much.
Once its allocated, it won't be released unless the OS asks.
You can use the DMVs to determine what memory is allocated to what pools within SQL's memory space, but if it's allocated then it is being 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
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply