Will SQL just chew about all of the resources it has available? We added two more gigs last night and it used it up. If this is normal, then I change the thresholds on "Target - Total Server Memory. Thanks for your help!
Yes, that's normal. SQL Server will grow into the max server size you set for the instance and not release the memory (even if not in active use). Remember when setting the max server size to leave some room for the OS and anything else that may be/need to run on that host. If we're talking about a VM, then that brings in other things to consider like reservations in the VM config.
Same problem here... with SolarWinds DB instance
I am not a DBA guys - can anyone please help with resolving this issue? Where do I need to set SQL memory limit and how much should that be? (percentage of total OR just simply leave certain amount for OS - in this case how much to leave?)
To limit the amount of memory SQL Server uses...
easy peasy lemon squeezy
Thank a million brianflynn
brianflynn,
I have done this change and restarted the whole box, however, memory still maxed out and AppInsights is reporting 0kb free again. Is anything else I can check?
I think the definition we posted for this metric should be updated. It should first state that there is nothing inherently wrong with SQL Server’s total memory equaling the target memory thus resulting in this metric equaling zero. If Total Server Memory is less than Target Server Memory, resulting in this metric being a positive number, it *might* be a sign of memory pressure, but only if you have evidence that the database instance needs to use memory in which case this may indicate it can’t get the memory it needs (memory pressure). This would be more clearly indicated by the Memory Grants Pending metric. Of course if you are facing this challenge, you may wish to know what queries are causing this and to do that, you need to leverage SQL Server wait time analysis to identify the queries that suffer from memory pressure. Here is a blog post explains troubleshooting memory pressure with both system metrics and wait time analysis. If you have Database Performance Analyzer, wait time analysis is easy because you can look through the Trends view to check for the existence of wait types like RESOURCE_SEMAPHORE, which indicate a query waiting on memory.
