Applies To: SQL Server 2014, SQL Server 2016 Preview
Returns the status of each hand for a specific cache clock.
Applies to: SQL Server (SQL Server 2008 through current version), Azure SQL Data Warehouse Public Preview.
To call this from SQL Data Warehouse, use the name sys.dm_pdw_nodes_os_memory_cache_clock_hands.
Address of the cache associated with the clock. Is not nullable.
Name of the cache. Is not nullable.
Type of cache store. There can be several caches of the same type. Is not nullable.
Type of hand. This is one of the following:
Is not nullable.
Status of the clock. This is one of the following:
Is not nullable.
Number of sweeps made through the cache to remove entries. Is not nullable.
Number of entries removed by all sweeps. Is not nullable.
Number of entries updated during the last sweep. Is not nullable.
Number of entries removed during the last sweep. Is not nullable.
Last time, in milliseconds, that the clock hand moved. Is not nullable.
Time, in milliseconds, of the previous sweep. Is not nullable.
Total time, in milliseconds, taken by the clock to complete the previous round. Is not nullable.
Requires VIEW SERVER STATE permission on the server.
SQL Server stores information in memory in a structure called a memory cache. The information in the cache can be data, index entries, compiled procedure plans, and a variety of other types of SQL Server information. To avoid re-creating the information, it is retained the memory cache as long as possible and is ordinarily removed from the cache when it is too old to be useful, or when the memory space is needed for new information. The process that removes old information is called a memory sweep. The memory sweep is a frequent activity, but is not continuous. A clock algorithm controls the sweep of the memory cache. Each clock can control several memory sweeps, which are called hands. The memory-cache clock hand is the current location of one of the hands of a memory sweep.