Releases memory occupied by SQLServer

Reprinted to: Memory releases the memory technology occupied by SQL Server, SQL Server, memory, and memory. Due to the amount of memory management policies of SQL Server for the system

Reprinted to: http://www.imkevinyang.com/2009/09/%E9%87%8A%E6%94%BEsql-server%E5%8D%A0%E7%94%A8%E7%9A%84%E5%86%85%E5%AD%98.html releases the memory occupied by SQL Server Technology casual SQL, SQL Server, memory, memory release due to the SQL Server for the system memory management policy is how much

Reproduced to: http://www.imkevinyang.com/2009/09/%E9%87%8A%E6%94%BEsql-server%E5%8D%A0%E7%94%A8%E7%9A%84%E5%86%85%E5%AD%98.html
ReleaseSQL ServerOccupiedOfMemory

SQL, SQL Server,Memory,MemoryRelease

Because SQL ServerMemoryUnless the systemMemoryInsufficient (about to remainingMemoryAbout 4 MB ).ReleaseA little bitMemory. Therefore, we often find that the system that runs SQL ServerMemoryIt is always high.

TheseMemoryIt is generally used as a cache when SQL Server is running. For example, if you run a select statement, SQL Server willRelated(The data operated by SQL Server is in the unit of pages) loadedMemoryIf you request the data on this page again, you do not need to read the disk, greatly improving the speed. This type of cache is called data cache. There are other types of cache. For example, when executing a stored procedure, SQL Server needs to compile and run the program first, and the compiled results will also be cached. You do not need to compile the program again next time. If these caches are no longer needed, we can call the following DBCC management commands to clear these caches:

DBCC FREEPROCCACHEDBCC FREESESSIONCACHEDBCC FREESYSTEMCACHE('All')DBCC DROPCLEANBUFFERS

These commands are used to clear the Stored Procedure respectively.RelatedCache, session cache, system cache, and all caches. For more information, see MSDN.

However, although these commands will clear the existing cache and leave a place for the new cache, SQL server does notReleaseDrop alreadyOccupiedOfMemory. However,SQL Server does not provide any command to allow usReleaseNoMemory. Therefore, we can only dynamically adjust the available physicalMemorySet to force itReleaseMemory.

USE master -- open advanced settings EXEC sp_configure 'show advanced options', 1 reconfigure with override -- set the physicalMemoryUp to 1 GEXEC sp_configure 'max server memory (MB) ', 1024 reconfigure with override -- restore the original upper limit EXEC sp_configure 'max server memory (MB )', 5120 reconfigure with override -- Restore Default EXEC sp_configure 'show advanced options', 0 RECONFIGURE WITH OVERRIDE

We can also use the SQL Server Management Enterprise Manager for dynamic control. Connect to the Enterprise Manager, open the properties Panel of the SQL Server instance, and findMemoryChange the maximum ServerMemory.

--Kevin Yang