May 23, 2019 at 3:57 pm
Good day)
I'm sorry for my English
server 2016 Ent
I have a problem with memory leaks
SELECT
sqlserver_start_time,
physical_memory_kb/1024/1024 physical_memory_GB,
committed_kb/1024/1024 committed_GB,
committed_target_kb/1024/1024 committed_target_GB,
visible_target_kb/1024/1024 visible_target_GB
-- stack_size_in_bytes/1024/1024/1024 stack_size_GB
FROM sys.dm_os_sys_info(nolock)
physical_memory_GB =1023 committed_GB = 874
I try to freeproccache, buffercache, but this dont't help, only restart service help solve this problem for a while
Thanks for the answers)
May 23, 2019 at 3:59 pm
What makes you think that this is a memory leak?
The absence of evidence is not evidence of absence
- Martin Rees
The absence of consumable DDL, sample data and desired results is, however, evidence of the absence of my response
- Phil Parkin
May 23, 2019 at 6:42 pm
What are you expecting needs the RAM that SQL Server is holding on to? Freeing buffer or proc cache won't necessarily reduce how much RAM SQL Server is using, it just forces SQL Server to clean out the items that it is holding in that memory. RAM is important for SQL Server, you don't want every request to have to be read from disk.
The way memory management works in SQL Server, the system will start taking more RAM as it needs it for things like data or query execution plans. SQL Server will try to hold onto that RAM once it has been assigned and manages itself what is stored in that memory, based on how recently that information has been used. SQL Server can give memory back if the operating system asks it to.
Here is an article that talks about how to help control the settings of the maximum RAM and minimum RAM SQL Server tries to use:
May 24, 2019 at 7:07 am
Chris Harshman
Phil Parkin
Thank's you very much for your answers, I will try to figure it out.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply