Every time SQL Server is enabled on a machine, the memory will be very tight whether or not it is used for SQL-related work. Today, I saw this in my book. I Googled it online and found related content on the MS website. Memory usage:
The high usage of memory by SQL Server is not a problem of Memory leakage, but the expected behavior of the SQL Server Buffer Pool. It will be used for reference based on the system's reported memory surplus, and occupies only about 4-10 MB of physical memory for system page swap.
In addition, the "maximum memory of the server" set by the server only represents the maximum limit of the SQL Server Buffer Pool, and does not represent the allocation of other parts by the SQL server, therefore, the memory usage of SQL Server sometimes exceeds the limit of "maximum memory of the server.
See the original http://support.microsoft.com/default.aspx? SCID = KB; ZH-CN; 321363 How to determine the memory demand of sqlserver:
To check whether SQL Server has enough memory, you can monitor the memory: abailable bytes counter. If the value is less than 5 MB, SQL Server requests more physical memory.
To monitor the memory usage of SQL Server, refer to the following two counters:
Sqlserver: Memory manger: Total server memory (Kb) Total server memory, which refers to all applications on the current SQL Server server.ProgramTotal memory used;
Sqlserver: Memory Manager: targen Server Manager (Kb) memory of the target server. Memory size required to improve the efficiency of SQL Server. In addition:
Process: working set. If this value continuously falls below the memory usage configured by SQL Server, it indicates that more than enough memory is configured for it.
Buffer cache hit ratio, indicating the percentage of pages found in the cache instead of being read from the disk. A well-designed system should be 90-95%, which may increase the hit rate by increasing the memory. |
