The Tempdb panel tracks the status of the tempdb database on your monitored SQL Server instance. Unexpected spikes in the use of tempdb usage and space may warn you to allocate additional space to prevent tempdb issues from causing a performance issue on your server. For additional information, see.
Problems with tempdb can cause an entire SQL Server instance to become inoperable.
Tempdb Space Used chart
The Tempdb Space Used chart provides different views of how your database is used over time based on the object type. Tempdb can fill up quickly when you are low on disk space and or have a low maximum size for database growth. In environments where read committed snapshot isolation is in use, long running transactions may also cause rapid growth in tempdb.
Why it is important
Indicates the amount of tempdb space used by internal objects.
Indicates the amount of tempdb space used by mixed extents.
Indicates the amount of tempdb space used by user objects.
Indicates the amount of tempdb space used by the version store.
Tempdb Contention chart
The Tempdb Contention chart provides the latch wait time for the allocation pages of your tempdb. These latch waits are associated with performance degradation for the related queries. Latch contention is usually an indication that you should create additional tempdb data files or if you already have multiple files, make adjustments so they are equally sized. For more information about tempdb contention, see.
Why it is important
Indicates the latch wait time for the global allocation map pages of tempdb.
Indicates the latch wait time for the page free space pages of tempdb.
Indicates the latch wait time for the shared global allocation map pages of tempdb.
Version Store Cleanup Rate
The Version Store Cleanup Rate gauge displays the current version store cleanup rate and the version generation rate of the data rows necessary to support snapshot isolation. Maintaining a cleanup rate above or equal to the generation rate helps you avoid filling up tempdb. Note that long-running snapshot isolation transactions prevent cleanup of older entries in the tempdb version store, causing growth which can affect performance and cause tempdb to run out of space. When interpreting this gauge, note that version store cleanup occurs only once per minute while generation may be ongoing. For more information about tempdb version store, see .