Page History
...
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.
Metric | Why it is important |
---|---|
Internal | Indicates the amount of tempdb space used by internal objects. |
Mixed | Indicates the amount of tempdb space used by mixed extents. |
User | Indicates the amount of tempdb space used by user objects. |
Version Store | Indicates the amount of tempdb space used by the version store. |
Anchor | ||||
---|---|---|---|---|
|
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 Monitor your tempdb database.
Metric | Why it is important |
---|---|
GAM Page | Indicates the latch wait time for the global allocation map pages of tempdb. |
PFS Page | Indicates the latch wait time for the page free space pages of tempdb. |
SGAM Page | Indicates the latch wait time for the shared global allocation map pages of tempdb. |
Anchor | ||||
---|---|---|---|---|
|
...
Scroll pdf ignore |
---|
SQL Diagnostic Manager identifies and resolves SQL Server performance problems before they happen. Learn more > > |