Lokasi ngalangkungan proxy:   [ UP ]  
[Ngawartoskeun bug]   [Panyetelan cookie]                
Skip to content

Commit 83c82bc

Browse files
authored
Merge pull request #7995 from MicrosoftDocs/release-sqlseattle
Release sqlseattle
2 parents d7e042d + dfb12ae commit 83c82bc

2 files changed

Lines changed: 38 additions & 2 deletions

File tree

Lines changed: 33 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,33 @@
1+
---
2+
title: "Hybrid Buffer Pool | Microsoft Docs"
3+
ms.custom: ""
4+
ms.date: "11/06/2018"
5+
ms.prod: sql
6+
ms.prod_service: high-availability
7+
ms.reviewer: ""
8+
ms.technology: configuration
9+
ms.topic: conceptual
10+
ms.assetid:
11+
author: DBArgenis
12+
ms.author: Argenis.Fernandez
13+
manager: craigg
14+
---
15+
# Hybrid Buffer Pool
16+
[!INCLUDE[appliesto-ss-xxxx-xxxx-xxx-md](../../includes/appliesto-ss-xxxx-xxxx-xxx-md.md)]
17+
18+
With SQL Server 2019 CTP 2.1 a new feature is introduced in the SQL Server database engine which allows it to directly access data pages in database files stored in persistent memory (PMEM) devices.
19+
20+
In a traditional system without persistent memory, SQL Server caches data pages in the buffer pool. With Hybrid Buffer Pool, SQL Server skips performing a copy of the page into the DRAM-based portion of the buffer pool, and instead references the page directly on the database file that lives on a PMEM device. Access to data files in PMEM for Hybrid Buffer Pool is performed using memory-mapped I/O, also known as enlightenment.
21+
22+
Only clean pages can be referenced directly on a PMEM device. When a page becomes dirty it is kept in DRAM, and then eventually written back to the PMEM device.
23+
24+
This feature is available on both Windows and Linux.
25+
26+
## Enable Hybrid Buffer Pool
27+
28+
On CTP 2.1, you must enable the startup trace flag 809 in order to use Hybrid Buffer Pool.
29+
30+
## Best Practices for Hybrid Buffer Pool
31+
32+
* When formatting your PMEM device on Windows use the largest allocation unit size available for NTFS (2MB in Windows Server 2019) and ensure the device has been enabled for DAX (DirectAccess)
33+

docs/sql-server/what-s-new-in-sql-server-ver15.md

Lines changed: 5 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -35,6 +35,7 @@ Community technology preview (CTP) 2.1 is the latest public release of [!INCLUDE
3535
- UTF-8 collations support in [!INCLUDE[ssNoVersion](../includes/ssnoversion-md.md)] setup
3636
- Use derived table or view aliases in graph match queries
3737
- Improved diagnostic data for stats blocking
38+
- Hybrid Buffer Pool
3839
- [Tools](#tools)
3940
- Azure Data Studio
4041

@@ -285,9 +286,11 @@ Any [!INCLUDE[ssNoVersion](../includes/ssnoversion-md.md)] file that is placed o
285286
> [!NOTE]
286287
> For this preview release, enlightenment of files on persistent memory devices is only available on Linux. SQL Server on Windows supports persistent memory devices starting with SQL Server 2016.
287288
288-
### Hybrid Buffer Pool (CTP 2.1)
289+
### Hybrid buffer pool (CTP 2.1)
289290

290-
Hybrid Buffer Pool is a new feature of the SQL Server database engine where database pages sitting on database files placed on a persistent memory (PMEM) device will be directly accessed when required. Since PMEM devices provide very low latency for data access, the engine can forgo making a copy of the data in a "clean pages" area of the buffer pool and simply access the page directly on PMEM. Access is performed using memory mapped I/O, as is the case with enlightenment. This brings performance benefits from avoiding a copy of the page to DRAM, and from the avoidance of the I/O stack of the operating system to access the page on persistent storage. This feature is available on both SQL Server on Windows and SQL Server on Linux.
291+
Hybrid buffer pool is a new feature of the SQL Server database engine where database pages sitting on database files placed on a persistent memory (PMEM) device will be directly accessed when required. Since PMEM devices provide very low latency for data access, the engine can forgo making a copy of the data in a "clean pages" area of the buffer pool and simply access the page directly on PMEM. Access is performed using memory mapped I/O, as is the case with enlightenment. This brings performance benefits from avoiding a copy of the page to DRAM, and from the avoidance of the I/O stack of the operating system to access the page on persistent storage. This feature is available on both SQL Server on Windows and SQL Server on Linux.
292+
293+
For more information, see [Hybrid buffer pool](../database-engine/configure-windows/hybrid-buffer-pool.md)
291294

292295
### Support for columnstore statistics in DBCC CLONEDATABASE (CTP 2.0)
293296

0 commit comments

Comments
 (0)