Date: Thu, 28 Mar 2024 10:18:24 +0000 (UTC) Message-ID: <1789953478.67841.1711621104456@ip-10-0-1-26.ec2.internal> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_67840_1918562087.1711621104454" ------=_Part_67840_1918562087.1711621104454 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
The Tempdb panel tracks the statu= s 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 additi= onal space to prevent tempdb issues from causing a performance issue on you= r server. For additional information, see how to get the tempdb status summary.
Problems with tempdb can cause an entire SQL Server instance = to become inoperable.
The Tempdb Space Used chart provides diff= erent 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 l= ow maximum size for database growth. In environments where read committed s= napshot 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. |
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 tempd=
b data files or if you already have multiple files, make adjustments so the=
y are equally sized. For more information about tempdb contention, see
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 fr= ee space pages of tempdb. |
SGAM Page |
Indicates the latch wait time for the shared = global allocation map pages of tempdb. |
The <= strong>Version Store Cleanup Rate gauge displays the curre= nt version store cleanup rate and the version generation rate of the data r= ows necessary to support snapshot isolation. Maintaining a cleanup rate abo= ve 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 perfor= mance and cause tempdb to run out of space. When interpreting this gauge, n= ote that version store cleanup occurs only once per minute while generation= may be ongoing. For more information about tempdb version store, see Monitor your tempdb database.