Buffer pool extension (BPE) in SQL Server 2014 CPT2

Buffer pool extension (BPE)

Memory is one of the key assets available for the SQL Server and especially buffer pool memory, which plays key role in storing data pages and in turn reducing the I/O demand.

The Buffer Pool Extension feature (BPE) provides the seamless integration of solid-state drives (SSD) as a nonvolatile random access memory (NvRAM) extension to the Database Engine buffer pool to significantly improve I/O throughput.

Solid-state drives (SSD) have some advantages over direct memory :

· the higher flexibility of storage options over memory options;

· is the greater price efficiency of available storage vs. memory.

· Buffer Pool Extension offer:

· Performance gains on OLTP workloads, mostly on the read-heavy OLTP.
· No risk of data loss. BPE only deals with clean pages.
· No application modification required. Just enable the feature and you’re ready to go.
· Simple feature syntax

SQL Server 2014 CP Buffer pool extension (BPE)
T2
Eg:
ALTER SERVER CONFIGURATION
     SET BUFFER POOL EXTENSION ON
     SIZE = 50 GB
     FILENAME = 'F:\SSDCACHE\EXAMPLE.BPE'

Comments

SQL Server script Error: Insufficient result space to convert uniqueidentifier value to char.

Error: G etting below error while trying to copy data from one table to another: Msg 8170, Level 16, State 2, Line 1004 Insufficient result space to convert uniqueidentifier value to char. Fix: UserID column which would be having Unique identifier data require more space (36 character). Size is specified as 15 here. To fix it just specify 36 as varchar length or specify Uniqueidentifier as data type for UserID column.

While executing Select query to pull data from a different server, SQL Server is showing following error:

Msg 7202, Level 11, State 2, Line 1 Could not find server 'LAPTOP-09O6NE3K\SQLEXPRESS03' in sys.servers. Verify that the correct server name was specified. If necessary, execute the stored procedure sp_addlinkedserver to add the server to sys.servers. Completion time: 2024-02-05T17:18:24.6869756+05:30 Solution: Step1: Check if the server is available in the sys.servers table SELECT name from sys.servers Step2: If no, add the new server to the sys.servers table EXEC sp_addlinkedserver @server = 'server name' Eg" EXEC sp_addlinkedserver @server = 'LAPTOP-09O6NE3K\SQLEXP RESS03' Step3: Recheck if the new server name is added to the sys.servers table. If yes, try then rerunning the select query which throwed the error. Now it should pull data from the table in the new server successfully.

Overcoming Performance Issues with Memory Optimized tables - SQL Server 2014 CPT2

Overcoming Performance Issues with Memory Optimized tables - SQL Server 2014 CPT2 1. Problem Tuning databases so that they provide the best possible performance is one of the most important responsibilities of database administrators (DBAs). SQL Server was originally designed at a time when it could be assumed that main memory was very expensive, so data needed to reside on disk except when it was actually needed for processing. As the amount data within an organization increases, accumulation of data affects the productivity of DBAs, who must spend considerable time and effort on achieving the high levels of database performance. 2. Solution Nowadays memory is much cheaper and a working data set can be stored entirely in memory. The assumption that main memory was very expensive is no longer valid as memory prices have dropped enormously. Memory-opti...

TSQL Masters

Search This Blog