Skip to content

Commit c28c33d

Browse files
authored
Merge pull request #20568 from WilliamDAssafMSFT/20211028-asdb-mi-tempdb-memopt-metadata
20211028 asdb mi tempdb memopt metadata
2 parents 86b5c5b + 2dd0366 commit c28c33d

1 file changed

Lines changed: 7 additions & 5 deletions

File tree

docs/relational-databases/databases/tempdb-database.md

Lines changed: 7 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,8 +1,8 @@
11
---
22
title: "tempdb database"
3-
description: This topic provides details about the configuration and use of the tempdb database in SQL Server and Azure SQL Database.
3+
description: This article provides details about the configuration and use of the tempdb database in SQL Server and Azure SQL Database.
44
ms.custom: "P360"
5-
ms.date: 07/02/2021
5+
ms.date: 10/28/2021
66
ms.prod: sql
77
ms.prod_service: "database-engine"
88
ms.technology:
@@ -226,11 +226,12 @@ Metadata contention in `tempdb` has historically been a bottleneck to scalabilit
226226

227227
This feature effectively removes this bottleneck and unlocks a new level of scalability for tempdb-heavy workloads. In [!INCLUDE[sql-server-2019](../../includes/sssql19-md.md)], the system tables involved in managing temporary table metadata can be moved into latch-free, non-durable, memory-optimized tables.
228228

229+
Currently the memory-optimized tempdb metadata feature is not available in Azure SQL Database or Azure SQL Managed Instance.
230+
229231
Watch this seven-minute video for an overview of how and when to use memory-optimized tempdb metadata:
230232

231233
> [!VIDEO https://channel9.msdn.com/Shows/Data-Exposed/How-and-When-To-Memory-Optimized-TempDB-Metadata/player?WT.mc_id=dataexposed-c9-niner]
232234
233-
234235
### Configuring and using memory-optimized tempdb metadata
235236

236237
To opt in to this new feature, use the following script:
@@ -342,10 +343,11 @@ SELECT R2.session_id,
342343
FROM sys.dm_db_session_space_usage AS R1
343344
INNER JOIN sys.dm_db_task_space_usage AS R2 ON R1.session_id = R2.session_id
344345
GROUP BY R2.session_id, R1.internal_objects_alloc_page_count,
345-
R1.internal_objects_dealloc_page_count;;
346+
R1.internal_objects_dealloc_page_count;
346347
```
347348

348-
## Related content
349+
## Next steps
350+
349351
- [SORT_IN_TEMPDB option for indexes](../../relational-databases/indexes/sort-in-TempDB-option-for-indexes.md)
350352
- [System databases](../../relational-databases/databases/system-databases.md)
351353
- [sys.databases](../../relational-databases/system-catalog-views/sys-databases-transact-sql.md)

0 commit comments

Comments
 (0)