Menu
I am debugging one of my apps and noticed that the RAM on my SQL Server 2005 x64 box (running on a Windows 2003 R2 x64 ) is pegged and even going into the paging file.
I understand that SQL Server 2005 x64 just grabs everything it can, so this might be normal (???). How can I check how much memory it is actually using?
732
SQL Server will consume as much memory as you will allow it. By default, that number would encompass 100% of your numerical memory on your machine. SQL Server will dynamically use memory, so even if you set max memory to 12 GB if SQL requires, it will use memory to 12 GB.
Max Server Memory is set at the instance level: right-click on your SQL Server name in SSMS, click Properties, Memory, and it's “Maximum server memory.” This is how much memory you're willing to let the engine use.
You need to run Perfmon (start->control panel->administrative tools->performance). The counters you want, I believe, are in SQL Server:Memory Manager. Target Server Memory is how much it's allowed to take if needed, Total Server Memory is how much it's currently using. If you click on Explain it'll pop open a box with the details.
By default it's uncapped, and should use all but a couple gb of memory (it leaves that for the OS). However, there are various bugs and memory leaks that can cause it to go into paging.
55
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
