SQL Server views the cache and reasonably sets the maximum memory

SQL Server servers run for a while to discover that memory has soared to 98% (the first time this problem was thought to be a virus, Trojan, system to crash ...) Later, I have been groping for some time to share our experience.

Workaround:

1. Restarting the host

2. Restart SQL Server Services

3. Set Maximum memory

The first two methods are not suitable for the online environment and the indicator does not recommend setting the maximum memory

If there are SQL Server servers constantly eating memory besides adding physical memory, it is recommended to run a command to see how much memory the current database consumes

Select Counter_name, LTrim (cntr_value*1.0/1024/1024) + ' G ' as MEMORYGB from Master.sys.dm_os_performance_counters

where counter_name like '%target%server%memory% ' or counter_name like '%total%memory% '

650) this.width=650; "src=" http://s3.51cto.com/wyfs02/M02/6F/5E/wKiom1WaJxvy5nrKAAGTkHKi43E531.jpg "title=" 00.png "alt=" Wkiom1wajxvy5nrkaagtkhki43e531.jpg "/>

Then based on the return value to determine whether the current system memory is not a problem with SQL Server if the cache is very large recommended to set the maximum cache 8G memory My environment is to give SQL Server 7G reserved 1G to the system

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M00/6F/5B/wKioL1WaKa6xxsOxAAJ8M2KCBoo942.jpg "Title=" 000. PNG "alt=" wkiol1waka6xxsoxaaj8m2kcboo942.jpg "/>

In addition, Windows Server may sometimes occur when the system process takes up a lot of memory, both of the two servers may have occurred because the system did not activate the patch has not been caused by the general restart after the normal restart (the online environment restart, it is almost a small heart to jump out) so or hurry to activate it ...

This article is from the "Rich Master" blog, please be sure to keep this source http://7380705.blog.51cto.com/7370705/1671318

SQL Server views the cache and reasonably sets the maximum memory