SQL Server servers run for a while to find that memory is growing exponentially to 98%. Workaround: Restart the host computer to restart the SQL Server service setting maximum memory the first two methods are less suitable for the online environment and the indicator does not recommend setting the maximum memory if there are SQL Server servers constantly eating memory In addition to 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% ' 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 SQL Server 7G Reserved 1G for System wkiol1waka6xxsoxaaj8m2kcboo942.jpg In addition, Windows servers can sometimes occur when the system process takes up a lot of memory, both of which may have occurred because the system did not activate the patch after the general restart caused by the Back to normal (the online environment restart, almost a small heart to jump out) so let's activate it ...
SQL Server views the cache and reasonably sets the maximum memory
