May 6, 2014 at 11:03 am
Never use task manager to check SQL's memory. It reports incorrect values when SQL is using locked pages.
The page size is not a concern, 8GB is probably what you have it set to be. The 200 MB is not an accurate memory usage for SQL, so no, it is not a concern.
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
May 6, 2014 at 11:08 am
oh so its the lock pages that skews those results.
what is an accurate way to get how much memory sql is actually using so i can show my boss the memory is being used?
Thanks for all your help.
May 6, 2014 at 12:57 pm
Well, not skews results so much as causes task manager to mis-report.
Performance Monitor. Easiest is total server memory under (I think) the SQL Server Memory Manager. You can also go to the process object, find sqlservr.exe and look at all the memory-related counters there.
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
May 6, 2014 at 1:22 pm
Thanks I used one of the Dyamic views that I found and it shows 6.5 gigs so we are good. Way to go task manager.
Thanks for all the help
May 7, 2014 at 3:49 am
I will try to test this but have very limited time over the next 2 weeks.
Original author: https://github.com/SQL-FineBuild/Common/wiki/ 1-click install and best practice configuration of SQL Server 2019, 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005.
When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist - Archbishop Hélder Câmara
Viewing 5 posts - 31 through 34 (of 34 total)
You must be logged in to reply to this topic. Login to reply