sql server 2016 - connect(); //2016 recap

03/05/2023 SQL SERVER 2016 RECAP - Hungpt 1

CONNECT(); //2016 RECAP

SQL SERVER 2016

Ph m Ti n Hùngạ ế[email protected]

mailto:[email protected]


Nội dung1. Nh ng con s th ng kêữ ố ố

2. Security

3. Performance

4. Seamless Integration

5. Database engine enhancements


1. Những con số thống kê


2. Security

• Use cases

• Client and Data On-Premises

• Client On-Premises with Data in Azure

• Client and Data in Azure

Always Encrypted – Use cases


2. SecurityAlways Encrypted – How it works

App

SELECT Name FROM Patients WHERE SSN=@SSN

@SSN='198-33-0987'Column

EncryptionKey

Jane Doe

Name1x7fg655se2e

SSNUSA

Country

Jim Gray 0x7ff654ae6d USA

John Smith 0y8fj754ea2c USA

dbo.Patients

Result Set

Jim Gray

Name

Query

Application - Trusted SQL Server - Untrusted

SELECT Name FROM Patients WHERE SSN=@SSN

@SSN=0x7ff654ae6d

EnhancedADO.NET

Library

SQL Server Native Client

.NET 4.6

Column

MasterKey

Gianluca Sartori ,SQL Server 2016 New Security Features


2. SecurityRow Level Security – Use cases

• Use cases:

• Doanh nghi p mu n ệ ố gi i h n thông tin truy ớ ạc p ậ v d li u bán hàng c a t ng đ n v .ề ữ ệ ủ ừ ơ ị

• Multi-tenant Application


2. SecurityRow Level Security – How it works

LATAM Salesperson

EMEA Salesperson

Evil Inc.

NameEMEA

Area2.500

Budget

Wealthy Corp. LATAM 2.350

Greedy Corp. APAC 1.500

dbo.Customer

Manager

APAC Salesperson



2. SecurityRow Level Security – How it works

EMEA Salesperson

Evil Inc.

NameEMEA

Area2.500

Budget

Wealthy Corp. LATAM 2.350

Greedy Corp. APAC 1.500

dbo.Customer

DBA

Security Policy

SELECT *FROM Customer

SELECT *FROM CustomerAPPLY itvf_securityPredicate()



3. Performance

• Use cases:

• High-throughput and low-latency transaction

processing

• Data ingestion, including IoT (Internet-of-

Things)

• Caching and session state

• Tempdb object replacement

Hekaton (In Memory OLTP) – Use cases


3. PerformanceFeature / Limitation SQL Server 2014 SQL Server 2016 CTP2 (07/2015)Maximum memory for memory-optimized tables Recommendation (not hard limit): 256

GBRecommendation (not hard limit): 2TB

Alter memory-optimized tables (after creation) Not Supported Supported

Alter natively-compiled stored procedures Not Supported Supported

Transparent Data Encryption (TDE) Not Supported Supported

LEFT and RIGHT OUTER JOINSELECT DISTINCTOR and NOT operatorsSubqueries in all clauses of a SELECT statementNested stored procedure callsUNION and UNION ALLAll built-in math functions….

Not Supported Supported

Hekaton (In Memory OLTP) – Enhancements

Artemakis Artemiou, Introducing SQL Server In-Memory OLTP



• Use cases:

• Query plan changes troubleshooting

• Force plans from history

Query Store – Use cases


4. Database engine enhancementsQuery Store – How it works



• Use cases:

• The size of tables is getting out of

control.

• Rarely access cold data

• Have to keep buying and adding

more storage

• Can’t backup or restore such large

tables within the SLA

Stretch Database



• Use cases:

• Integrate with Hadoop, Azure blob

storage without Learning New Tools &

changing code base.

• Integrate with BI tools (which is

compatible with SQL Server)

• Export data to Hadoop or Azure blob

storage

Polybase – Use cases


4. Seamless IntegrationPolybase – How it works



• Use cases:

• Want to storage data in JSON format.

• Don’t want to learning new tools and

integration

Native JSON support – Use cases


5. Database engine enhancementsNative JSON support – Use cases


High-end Features

sql server 2016 - connect(); //2016 recap

Engineering