1. What’s new in
SQL Server 2016
James Serra
Big Data Evangelist
Microsoft
JamesSerra3@gmail.com
2. About Me
Microsoft, Big Data Evangelist
In IT for 30 years, worked on many BI and DW projects
Worked as desktop/web/database developer, DBA, BI and DW architect and developer, MDM
architect, PDW/APS developer
Been perm employee, contractor, consultant, business owner
Presenter at PASS Business Analytics Conference, PASS Summit, Enterprise Data World conference
Certifications: MCSE: Data Platform, Business Intelligence; MS: Architecting Microsoft Azure
Solutions, Design and Implement Big Data Analytics Solutions, Design and Implement Cloud Data
Platform Solutions
Blog at JamesSerra.com
Former SQL Server MVP
Author of book “Reporting with Microsoft SQL Server 2012”
3. SQL Server 2016 SP1: Everything built-in
The above graphics were published by Gartner, Inc. as part of a larger research document and should be evaluated in the context of the entire document. The Gartner document is available upon request from Microsoft. Gartner does not endorse any vendor, product or service depicted in its research
publications, and does not advise technology users to select only those vendors with the highest ratings or other designation. Gartner research publications consist of the opinions of Gartner's research organization and should not be construed as statements of fact. Gartner disclaims all warranties,
expressed or implied, with respect to this research, including any warranties of merchantability or fitness for a particular purpose.
Most consistent experience from on-premises to cloud
Microsoft Tableau Oracle
$120
$480
$2,230
Self-service BI per user
In-memory across all workloads
built-inbuilt-in built-in built-in built-in
TPC-H non-clustered results as of 04/06/15, 5/04/15, 4/15/14 and 11/25/13, respectively. http://www.tpc.org/tpch/results/tpch_perf_results.asp?resulttype=noncluster
at massive scale
0 1
4
0 0
3
0
34
29
22
15
5
22
16
6
43
20
69
18
49
74
3
0
10
20
30
40
50
60
70
80
2010 2011 2012 2013 2014 2015 2016
SQL Server Oracle MySQL2 SAP HANA TPC-H
Oracle
is #6#2
SQL Server
#1
SQL Server
#3
SQL Server
National Institute of Standards and Technology Comprehensive Vulnerability Database update 5/4/2015
1M
Predictions
per second
5. Faster I/O, Networks, and Dense Core CPUs
Customer Experience, Benchmarks, XEvent, and xperf
Scalability Partitioning Parallelism
More and
Larger
Dynamic
Response
Improved
Algorithms
6. Core Engine Scalability
Automatic Soft NUMA
Dynamic Memory Objects
SOS_RWLock
Fair and Balanced Scheduling
Parallel INSERT..SELECT
Parallel Redo
DBCC
DBCC Scalability
DBCC Extended Checks
TempDB
Goodbye Trace Flags
Setup and Automatic Configuration of Files
Optimistic Latching
I/O
Instant File Initialization is No Longer Hidden
Larger Data File Writes
Multiple Log Writers
Indirect Checkpoint Default Just Makes Sense
Log Stamping Pattern
Log I/O at the Speed of Memory
Spatial
Native Implementations
TVP and Index Improvements
Always On Availability
Groups
Turbocharged
Better Compression
AES-NI EncryptionFull blog series: http://aka.ms/sql2016faster
7. ColumnStore Indexes – SQL Server 2012+
In-Memory OLTP – SQL Server 2014+
Significant upgrades in SQL 2016!
10. Do more. Achieve more.
Mission critical platform Deeper Insights Hyperscale
In-Memory OLTP
Greater T-SQL surface area, terabytes of
memory supported, and higher number of
parallel CPUs
Query Store
A flight data recorder for your database
Always Encrypted
Sensitive data remains encrypted at all times,
with ability to query
Row-Level Security
Fine-grained access control for table rows
Dynamic data masking
Real-time obfuscation of data to prevent
unauthorized access
Enhanced Always On
Distributed Availability Groups, Basic
Availability Groups, Automatic Failover
Real-time operational analytics
Running of analytical workloads concurrently
with OLTP workloads
R Integration
Insights from data across SQL Server and
Hadoop with the simplicity of T-SQL
PolyBase
Insights from data across SQL Server and
Hadoop with the simplicity of T-SQL
Mobile BI/SSRS/SSAS
Mobile reports on SSRS with Mobile Report
Publisher. SSAS performance improvements
Temporal Tables, JSON
Track change history, integrate with modern
service easily
Stretch Database
Stretch operational tables in a secure manner
into Azure for cost-effective historic data
availability.
Enhanced backup to Azure
Faster restore times, 50% reduction in storage.
Larger DBs
11. What’s new in SQL Server 2016 & SP1
Performance Security Data Marts and
OLAP cubes
Business
Intelligence
Advanced
Analytics
Hybrid
• 24 cores max and 128
GB max memory
• In-memory OLTP
• Operational
analytics*
• Basic High Availability
• Query Store
• Temporal
• Always Encrypted
• Row-level security
• Dynamic data
masking
• Fine-grained
auditing
• Partitioning
• Compression
• In-memory
ColumnStore*
• Change data capture
• Data snapshot
• PolyBase
• JSON support
• Basic tabular (16GB
memory per instance)
• Modernized reports
• Pin report to Power BI
• Enhanced multi-
dimensional models
• Direct query of
indexed views
• Single-threaded
for RRE
• Connectivity to R
Open
• Stretch Database
• Backup to Azure
enhancements
• In-memory OLTP
• Operational
analytics**
• Always Encrypted
• Row-level security
• Dynamic data
masking
• Fine-grained
auditing
• Partitioning
• Compression
• In-memory
ColumnStore**
• Data snapshot
• PolyBase
• JSON support
• Modernized reports • Stretch Database
• Backup to Azure
ExpressStandard
24Cores,128GBmemory1GBmemory,max10GB
Bold items are newly available in these editions in SQL Server 2016 SP1
* Standard Edition: In-memory columnstore and Operational Analytics limited to 32 GB of memory and 2 parallel cores
** Express Edition: In-memory columnstore and Operational Analytics limited to 256 MB of memory and 1 core
13. ALTER TABLE Sales.SalesOrderDetail
ALTER INDEX PK_SalesOrderID
REBUILD
WITH (BUCKET_COUNT=100000000)
T-SQL surface area: New
{LEFT|RIGHT} OUTER JOIN
Disjunction (OR, NOT)
UNION [ALL]
SELECT DISTINCT
Subqueries (EXISTS, IN, scalar)
ALTER support
Full schema change support: add/alter/drop
column/constraint
Add/drop index supported
Surface area improvements
Almost full T-SQL coverage including scaler user-defined
functions
Improved scaling
Increased size allowed for durable tables; more sockets
Other improvements
MARS support
Lightweight migration reports
14. Optimizing query performance and costs
Query Store = flight data recorder for databases
Built-in query monitoring
• Negligible perf & storage overhead
• Survives failover, memory pressure, …
• Data ready when that incident happens
T-SQL interface and SSMS UX
Top insights into your workload
• Query and resource stats
• Query plans
Developer
App User
Azure
application On-premise
Developer needs to find and fix
the underlying problem, ASAP
Customer reports the issue
(app is slow/unresponsive)
15. trust boundary
"SELECT Name FROM Customers
WHERE SSN = @SSN","111-22-3333"
Always Encrypted
Protect data at rest and in motion, on-premises and in the cloud
Name
Wayne Jefferson
ADO .NET
Name
0x19ca706fbd9a
Result SetResult Set
Client
Name SSN Country
0x19ca706fbd9a 0x7ff654ae6d USA
SQL Server or SQL Database
"SELECT Name FROM Customers
WHERE SSN = @SSN",0x7ff654ae6d
ciphertext
Encrypted sensitive data and corresponding keys
are never seen in plaintext in SQL Server
dbo.Customers
ciphertext
Security
16. Fine-grained access control over specific rows in a
database table
Help prevent unauthorized access when multiple users
share the same tables, or to implement connection
filtering in multitenant applications
Administer via SQL Server Management Studio or SQL
Server Data Tools
Enforcement logic inside the database and schema
bound to the table.
Protect data privacy by ensuring the right access across rows
SQL Database
Customer 1
Customer 2
Customer 3
Row-level security
17. Configuration made easy in the new Azure
portal
Policy-driven at the table and column level, for
a defined set of users
Data masking applied in real-time to query
results based on policy
Multiple masking functions available (e.g. full,
partial) for various sensitive data categories
(e.g. Credit Card Numbers, SSN, etc.)
SQL Database
SQL Server 2016 CTP2
Table.CreditCardNo
4465-6571-7868-5796
4468-7746-3848-1978
4484-5434-6858-6550
Real-time data masking;
partial masking
Dynamic Data Masking
Prevent the abuse of sensitive data by hiding it from users
18. Audit success/failure of
database operations
Enhanced auditing for
OLTP with ability to track
history of record
changes
Transparent Data
Encryption support for
storage of In-memory
OLTP Tables
Backup encryption now
supported with
compression
Other security enhancements
19. Greater scalability:
Load balancing readable secondaries
Increased number of auto-failover targets
Log transport performance
Improved manageability:
DTC support
Database-level health monitoring
Group managed service account
AG_Listener
New York
(Primary)
Asynchronous data
Movement
Synchronous data
Movement
Unified HA Solution
Enhanced AlwaysOn Availability Groups
AG
Hong Kong
(Secondary)
AG
New Jersey
(Secondary)
AG
21. 0100101010110 SQL Server
OLTP
SQL Server
data warehouse
ETL
In-memory
ColumnStore
In-memory
OLTP
Real-time fraud
detection
Operational analytics
Single system for OLTP and real-time analytics
Fraud detected
2-24
hrs
22. Data Scientist
Interact directly with data
Built-in to SQL Server
Data Developer/DBA
Manage data and
analytics together
Built-in advanced analytics
Running R algorithms at massive data scale
Example Solutions
• Salesforecasting
• Warehouse efficiency
• Predictive maintenance
Relational Data
Analytic Library
T-SQL Interface
Extensibility
?
R
RIntegration
010010
100100
010101
Microsoft Azure
Marketplace
New R scripts
010010
100100
010101
010010
100100
010101
010010
100100
010101
010010
100100
010101
010010
100100
010101
• Credit risk protection
23. PolyBase
Query relational and non-relational data with T-SQL
T-SQL query
SQL Server Hadoop
Quote:
************************
**********************
*********************
**********************
***********************
$658.39
Jim Gray
Name
11/13/58
DOB
WA
State
Ann Smith 04/29/76 ME
24. Paginated reports
Design beautiful documents using updated
tools and new features
Mobile reports
Create responsive, interactive reports optimized
for mobile devices
Modern web portal
Consume both types of reports in one web
portal using modern browsers
SQL Server Reporting Services
25. Scale your tabular
models with support
for high end servers
More memory
More cores
Enhanced Analysis Services
Deliver high performance and scalability for your BI solutions
High-end server hardware
Capability
Parallel partition processing
NUMA optimization for tabular models
On-demand loading and paging
Tabular and MOLAP modeling enhancements
Benefits
29. Order history
Name SSN Date
Jane Doe cm61ba906fd 2/28/2005
Jim Gray ox7ff654ae6d 3/18/2005
John Smith i2y36cg776rg 4/10/2005
Bill Brown nx290pldo90l 4/27/2005
Sue Daniels ypo85ba616rj 5/12/2005
Sarah Jones bns51ra806fd 5/22/2005
Jake Marks mci12hh906fj 6/07/2005
Order history
Name SSN Date
Jane Doe cm61ba906fd 2/28/2005
Jim Gray ox7ff654ae6d 3/18/2005
John Smith i2y36cg776rg 4/10/2005
Bill Brown nx290pldo90l 4/27/2005
Customer data
Product data
Order History
Stretch to cloud
Stretch SQL Server into Azure (Stretch DB)
Stretch cold data to Azure with remote query processing
App
Query
Microsoft Azure
Jim Gray ox7ff654ae6d 3/18/2005
30. Managed backup
Granular control of the backup
schedule
Local staging support for faster
recovery and resilient to transient
network issues
Support for system databases
Support simple recovery mode
Backup to Azure block blobs
Cost savings on storage
Significantly improved restore
performance
More granular control over Azure
storage
Maximum backup size 12TB
Azure Storage snapshot
backup
Fastest method for creating
backups and running restores
Uses SQL Server db files on Azure
Blob Storage
Enhanced backup to Azure
32. Easy with SQL Server migration assistants
SSMA for Oracle
SSMA for Sybase
SSMA for DB2
SSMA for MySQL
SSMA for Access
34. Enterprise
Highly available mission-critical apps,
enterprise-scale data warehousing,
end-to-end mobile BI and advanced analytics
Licensing changes in 2016
More built-in to what you are already buying
Enterprise
Mission critical apps, large-scale data warehousing
Business Intelligence
Premium corporate and self-service BI
Standard
Basic database, reporting and analytics
Express
Easy to get started—free to use
SQL Server 2014 SQL Server 2016 SP1
Standard
Fully-featured database for modern,
mid-tier applications and data marts
Express
Lightweight applications—free to use
Developer
Fully-featured SQL Server
Developer
For non production workloads. Now free to use —get it at Dev
Essentials
35. SQL Server 2016 Service Pack 1
Only data solution to
encrypt your data at
rest and in motion
Connect your
relational data to
big data with PolyBase
Real-time operational
analytics without
impacting performance
Faster transactions,
faster queries with
In-memory*
Unparalleled choice
for developer tools
and languages
1 T-SQL
Java
C/C++
C#/VB.NET
PHP
Node.js
Python
Ruby
Advanced featured across editions
Making innovation more accessible to all applications
Delivers common programming surface across editions—no application re-write
37. Standard Enterprise
Maximum number of cores New 24 cores Unlimited
Maximum memory utilized per instance 128 GB OS Max
Maximum size 524 PB 524 PB
Basic high availability (2-node single database failover, non-readable secondary) New
Enterprise data management (Master Data Services, Data Quality Services)
Advanced OLTP (In-memory OLTP, Operational analytics*) New
Advanced HA (Always On - multi-node, multi-db failover, readable secondaries)
Security (Always Encrypted, row-level security, data masking, basic auditing, separation of duties) New
Transparent Data Encryption
Fuzzy grouping and look ups
Data warehousing (In-Memory ColumnStore*, partitioning, data compression, change data capture,
database snapshot)
New
Basic data integration (SSIS, built-in connectors)
Basic Corporate Business Intelligence (Multi-dimensional models, Basic tabular model) New
Mobile BI (Datazen) New
Advanced Corporate Business Intelligence (Advanced tabular model, Direct query,
in-memory analytics, advanced data mining)
New
Basic “R” integration (Connectivity to R Open, Limited parallelism for RRE) New
Advanced “R” integration (Full parallelism for RRE) New
Stretch Database New
Programmability (T-SQL, CLR, Service Broker, JSON, XML) New
SQL Server 2016 SP1 features by edition
*Memory core and limitations for SE and Exp Features in blue are newly available in Standard and Express since SQL Server 2016 SP1
38. SSIS improvements for SQL Server 2016
CTP2
AlwaysOn support
Incremental deployment of
packages
Improved project upgrade support
CTP3
Designer improvements
One designer multi-version support
OData V4 support
Power Query as a data source
AlwaysOn
Availability Groups
Secondary for
SSISDB
New York
(Primary)
New Jersey
(Secondary)
SSIS
DB
SSIS
DB
SQL Server 2012
SSIS Project X
SQL Server 2016
SSIS Project X
Improved project
upgrade
39. Performance and Scale
Overall performance and scale
improvements
Target of 15x performance
improvement for Excel add-in
Increased performance for bulk
entity based staging operations
Security Improvements
New security roles for more
granular permissions around read,
write and delete
Multiple system administrators
Manageability and Modeling
Archival of Transaction Logs
Reuse of entities across models
Support for compound keys
Allow the Name and Code attributes
to be renamed
MDS Improvements
40. Supports caching data with automatic, multiple TempDB
files per instance in multi-core environments
Reduces metadata and allocation contention for TempDB
workloads, improving performance and scalability
Enhanced database caching
41. Enhanced support for Windows Server
Hardware Acceleration for TDE Encryption/Decryption
Parallelizing the Decryption Built-in Function to Improve Read Performance
Results in dramatically better response times for queries with encrypted data columns
42. SQL Server
2008
SQL Server
2008 R2
SQL Server
2000XML ● KPIs
Compression ● Policy-Based Mgmt ● Programmability
PowerPivot ● SharePoint Integration ● Master Data Services
SQL Server
2012
AlwaysOn ● ColumnStore Index ● Data Quality Services ● Power View ● Cloud Connectivity
SQL Server
2014
In-Memory Across Workloads ● Performance & Scale ● Hybrid Cloud Optimized ● HDInsight ● Cloud BI
Management Studio ● Mirroring
SQL Server
2005
SQL Server
2016
Enhanced Always On ● In-Memory OLTP ● Stretch DB ● Temporal Tables ● Enhanced Backup to Cloud ● Polybase ● Real-Time
Operational Analytics ● Row-Level Security ● Query Store ● R Services● Always Encrypted ● Mobile BI
The evolution of Microsoft SQL Server
43. SQL Server 2016 SP1 Enterprise
Enterprise
Enterprise includes all Standard features.
• End-to-end mobile
BI on all major
platforms
• Enhanced direct
query
• In-memory
analytics
• Advanced data
mining
• Advanced tabular
• Web portal
experience (all
reports in 1 place)
• Modernized reports
• Pin report to Power
BI
• Enhanced multi-
dimensional
models
• Enhanced in-
memory
ColumnStore
• PolyBase in scale-
out configuration
(head and compute
nodes)
• Deployment rights
for APS
• Distributed query
processing
• Support for JSON
• Always Encrypted
• Row-level security
• Dynamic data
masking
• Enhanced
separation of duties
• Enhanced SQL
Server auditing
• Transparent data
encryption
• OS max cores and
memory
• Enhanced in-
memory OLTP
performance
• Operational
analytics
• Enhanced
AlwaysOn with no
domain join (WS
2016)
• Query Store
• Temporal
• In database
Advanced Analytics
• R integration with
massive parallel
processing for
performance and
scale
• Works with in-
memory
technology
• Run in database or
standalone
• Connectivity to R
Open
• Stretch
Database
• Enhanced
backup
to Azure
• Enhanced HA
and DR with
Azure – ease of
use, no domain
join (WS2016)
• SSIS integration
with Azure Data
Factory and
Azure SQL Data
Warehouse
• Direct query of indexed
views
• Multiple filestream
containers
• Service broker
44. SQL Server 2016 SP1 Standard
• Basic tabular
(16GB memory
per instance)
• Modernized reports
• Pin report to
Power BI
• Enhanced multi-
dimensional models
• PolyBase
(compute node
only)
• Support for
JSON
• Database
Snapshot
• Partitioning
• Compression
• In-memory
ColumnStore*
• Change data
capture
• Always Encrypted
• Row-level security
• Dynamic data
masking
• Basic auditing
• Separation of duties
• InMemory OLTP
• Operational
analytics
• 24 cores max and
128 GB max
memory
• 2-node single
database failover
(non-readable
secondary)
• Query Store
• Temporal
• Single-threaded
for RRE
• Connectivity to
R Open
Standard
• Stretch
Database
• Enhanced
backup
to Azure
• Direct query of indexed
views
• Multiple filestream
containers
• Service broker
*In-memory columnstore and Operational Analytics limited to 32 GB of memory and 2 parallel cores
45. What’s new in SQL Server 2016 since 2014
Mobile BI
Enhanced SSIS
Enterprise-grade Analysis Services
Advanced tabular models
JSON support
Enhanced DQS
Enhanced MDS
Enhanced Reporting Services
Temporal tables
In-memory analytics
Advanced data mining
Access to reports online or offline
Create mobile reports using the
SQL Server Mobile Report
Publisher
Consume with Power BI mobile
apps
Operational analytics
In-memory ColumnStore
Deployment rights for APS
Enhanced In-memory ColumnStore
for DW
PolyBase for simple T-SQL
to query structured and
unstructured data
Enhanced database caching
Up to 15,000 partitions
Transparent Data Encryption
Always Encrypted
Real-time operational analytics
with in-memory OLTP or on disk
In-memory for more applications
Unparalleled scalability with
Windows Server 2016, with 12TB
memory and Windows Server
2016 max cores
Multiple node failover clustering
(3 synchronous, up to 8 replicas)
SQL Server Development Tools in
Visual Studio
Query Store
Temporal support
R built-in to your T-SQL
RRE APIs with full parallelism and
no memory limits for
scale/performance
Built-in In-memory Advanced
Analytics
Advanced tabular model
Direct query
Advanced data mining
Stretch database
Partitioning for efficient
data loading
Hybrid scenarios with SSIS
Enhanced backup to Azure
Easy migration to the cloud
Simplified cloud DR with AlwaysOn
replicas
46. What’s new in SQL Server 2016 since 2012
Mobile BI
Enhanced SSIS
Enterprise-grade Analysis Services
Advanced tabular models
Enhanced multidimensional
models
JSON support
Enhanced DQS
Enhanced MDS
Enhanced Reporting Services
Temporal tables
In-memory analytics
Advanced data mining
Create mobile reports using the
SQL Server Mobile Report
Publisher
Consume with Power BI mobile
apps on all major platforms
Azure HDInsight Service
Pin report items to Power BI
Power Map for Excel
Mobile BI interfaces for Power BI
Operational analytics
In-memory ColumnStore
Deployment rights for APS
Enhanced In-memory ColumnStore
for DW
PolyBase for simple T-SQL to query
structured and unstructured data
Enhanced database caching
Up to 15,000 partitions
Analytics Platform System
Transparent Data Encryption
Always Encrypted
Enhanced separation of duties
CC certification at High Assurance
Level for 2014
Backup encryption support
Real-time operational analytics
with in-memory OLTP or on disk
In-memory for more applications
Unparalleled scalability with
Windows Server 2016, with 12TB
memory and Windows Server 2016
max cores
Enhanced AlwaysOn, with 8
secondaries and Replica Wizard
Multiple node failover clustering (3
synchronous, up to 8 replicas)
In memory OLTP
Buffer Pool Extension to SSDs
Enhanced query processing
Resource Governor adds IO
governance
SysPrep as cluster level
Predictable performance with
tiering of compute, network and
story with Windows Server 2012 R2
Delayed Durability
Clustered Shared Volume support,
VHDX support (Windows Server
2012 R2)
Manage on-premises and cloud
apps (System Center 2012 R2)
Query optimization enhancements
Query Store
Temporal support
R built-in to your T-SQL
RRE APIs with full parallelism and
no memory limits for
scale/performance
Built-in In-memory Advanced
Analytics
Advanced tabular model
Direct query
Advanced data mining
Stretch database
Partitioning for efficient
data loading
Hybrid scenarios with SSIS
Enhanced backup to Azure
Easy migration to the cloud
Simplified cloud DR with AlwaysOn
replicas
Simplified backup to Azure
Support for backup of previous
versions of SQL Server to Azure
Cloud back-up encryption support
Simplified cloud Disaster Recovery
with AlwaysOn replicas in Azure
VMs
New Azure Deployment UI for SQL
Server
Larger SQL Server VMs and
memory sizes available in Azure
47. Enhanced productivity and performance
Power View
Configurable reporting alerts
Reporting as SharePoint Shared Service
Build organization knowledge base
Connect to 3rd party data cleansing
providers
Master Data Hub
Master Data Services Add-in for Excel
Graphical tools in SSIS
Extensible object model
SSIS as a Server
Broader data integration with more
sources: DB vendors, cloud, Hadoop
Pipeline improvements
SQL Server Data Tools
Local DB runtime (Express)
Data-tier application component project
template
Data-Tier Application Framework (DAC Fx)
Interoperability support (ADO.NET,
ODBC, JDBC, PDO, ADO APIs and .NET
C/C++, Java, Linux and PHP platforms)
Enhanced support for ANSI SQL
standards
Transact-SQL Static Code Analysis tools
Transact-SQL code snippets
Intellisense
FileTable build on FILESTREAM
Remote Blob Storage with SharePoint
2010
Statistical Semantic Search
Spatial features, include Full Globe and
arcs
Large user-defined data types
Distributed Replay
Contained Database Authentication
System Center Management Pack
for SQL Server 2012
Windows PowerShell 2.0 support
Multi-server Management with SQL
Server Utility Control Point
Data Tier Application Component
What’s new in SQL Server 2016 since 2008 R2
Mobile BI
Enhanced SSIS
Enterprise-grade Analysis Services
Advanced tabular models
In-memory analytics
Enhanced multidimensional models
JSON support
Enhanced DQS
Enhanced MDS
Modern Reporting Services
Temporal tables
Advanced data mining
Create mobile reports using the SQL
Server Mobile Report Publisher
Consume with Power BI mobile apps
Azure HDInsight Service
Power BI
Power Map for Excel
Mash up data from different sources,
such as Oracle & Hadoop
HA for StreamInsight, complex event
processing
SQL Server Data Tools support for BI
Change Data Capture for Oracle
Import PowerPivot models into Analysis
Services
Transparent Data Encryption
Always Encrypted
Enhanced separation of duty
CC certification at High Assurance Level
for 2014
Backup encryption support
Enhanced separation of duties
Default schema for groups
SQL Server Audit
SQL Server fine-grained auditing
Real-time operational analytics with
in-memory OLTP or on disk
In-memory for more applications
Unparalleled scalability with Windows
Server 2016, with 12TB memory and
Windows Server 2016 max cores
Enhanced AlwaysOn, with 8 secondaries
and Replica Wizard
Multiple node failover clustering (3
synchronous, up to 8 replicas)
In memory OLTP
Buffer Pool Extension to SSDs
Enhanced query processing
Resource Governor adds IO governance
SysPrep as cluster level
Predictable performance with tiering of
compute, network and story with
Windows Server 2012 R2
Delayed Durability
Clustered Shared Volume support, VHDX
support (Windows Server 2012 R2)
Manage on-premises and cloud apps
(System Center 2012 R2)
Query optimization enhancements
Recovery Advisor
Windows Server Core
Live Migration
Online operations enhancements
Query Store
Temporal support
R built-in to your T-SQL
RRE APIs with full parallelism and no
memory limits for scale/performance
Built-in In-memory Advanced Analytics
Advanced tabular model
Direct query
Advanced data mining
SSDT in Visual Studio
Stretch database
Partitioning for efficient data loading
Hybrid scenarios with SSIS
Enhanced backup to Azure
Easy migration to the cloud
Simplified cloud DR with AlwaysOn
replicas
Simplified backup to Azure
Support for backup of previous
versions of SQL Server to Azure
Cloud back-up encryption support
Simplified cloud Disaster Recovery with
AlwaysOn replicas in Azure VMs
New Azure Deployment UI for SQL
Server
Larger SQL Server VMs and memory
sizes available in Azure
DAC enhancements: Import/export with
Azure SQL Database
SQL Server Data Tools
License Monthly (with SA)
Resource Governor enhancements
Snapshot backups to Azure via SQL
Server Management Studio
Operational analytics
In-memory ColumnStore
Deployment rights for APS
Enhanced In-memory ColumnStore
for DW
PolyBase for simple T-SQL to query
structured and unstructured data
Enhanced database caching
Up to 15,000 partitions
Analytics Platform System
49. Q & A ?
James Serra, Big Data Evangelist
Email me at: JamesSerra3@gmail.com
Follow me at: @JamesSerra
Link to me at: www.linkedin.com/in/JamesSerra
Visit my blog at: JamesSerra.com (where this slide deck is posted under the “Presentations” tab)
Notas do Editor
Fluff, but point is I bring real work experience to the session
Current leader in MQs across major workloads
Ahead of SAP, IBM in OLTP, close 2nd to Oracle
Leader in BI MQ 7 years running
Stronger DW position since ‘11
New entrant in Advanced Analytics MQ (Niche)
Gartner MQ (ODMS MQ) talking points (far-left MQ):
Land with Oracle Customers – Gartner points out through inquires and surveys how much customers hate Oracle’s pricing. In the report customers use words like “Lock-in”, “Draconian” to refer to Oracle pricing & licensing. They also mention how the number of customers looking for alternatives to Oracle are increasing. Point out to IT decision makers in customer accounts how Microsoft has a history of building in innovation (in-memory, HA, security, mobile BI, Advanced Analytics) from SQL Server 2008 to 2016, rather than requiring expensive add-ons.
Land with SAP HANA Customers – Gartner points out the number of issues customers are having with HANA. We need to land that HANA is over promising and under delivering and it’s a V1 release with number of product & service issues required for Tier 1 workloads (Gartner lists these in the report). If you compare Gartner MQ from 2014 to 2015, HANA moved backwards in the MQ in both execution and vision (highlight this to customers). Remember more SAP runs on Microsoft SQL Server than any other platform. Protect your accounts by ensuring IT decision makers in customer accounts understand the risk they are taking with HANA and cost of rewriting the application and recommend upgrading old SQL Server to SQL Server 2014 instead.
Land with existing SQL customers to drive upgrades – we are 6 months away from EOS for SQL Server 2005 and there is no better time to land this MQ along with the SQL Server 2014 and SQL Server 2016 pitch with customers to encourage modernization.
That this slide is a reminder of the SS2016 value prop and for the full talk track point to the link for the 2-slide mini pitch in Infopedia.
We have mapped our editions by feature to support these core value prop and facilitate customer discussions on the release.
________________________________________________________
Please ensure the NIST disclaimer of 5/4/2015 is always on the slide when showing Most Secure database along with the least vulnerable chart. Should we in the future not be least vulnerable then we need to updated Most Secure Database to Unparalleled Security.
http://www.tpc.org/tpch/results/tpch_perf_results.asp?resulttype=noncluster&version=2%&currencyID=0
http://www.gartner.com/technology/reprints.do?id=1-2PMFPEN&ct=151013&st=sb
1 min
2 min
1 min
1 min
3 min
Enhancements of SQL Server 2016 can be split in3 major categories…
3 minutes
Performance
Enhanced in-memory performance with up to 30x faster transactions, more than 100x faster queries than disk-based relational databases and real-time operational analytics.
Security Upgrades
Always Encrypted technology helps protect your data at rest and in motion, on-premises and in the cloud, with master keys sitting with the application, without any application changes.
High Availability
Even higher availability and performance than SQL Server 2014 of your AlwaysOn secondaries, with the ability to have up to three synchronous replicas, DTC support, and round-robin load balancing of the secondaries.
Scalability
Enhanced database caching across multiple cores and support for Windows Server 2016 that efficiently scale compute, networking, and storage in both physical and virtual environments.
17. What are the scalability and performance features in Enterprise Edition only?
* Enterprise edition allows maximum usage of computing capacity for database engine, Analysis Services, and Reporting Services. Standard edition limits computing capacity to the lesser of 4 sockets or 24 cores, maximum of 128 GB of memory for database engine, 32 GB memory available for In-memory OLTP and In-memory ColumnStore, maximum DOP of 2 for In-memory ColumnStore
queries, 16 GB of memory for Analysis Services in Tabular mode, 64 GB of memory for Analysis Services in MOLAP mode, and 64 GB of memory for Reporting Services.
* These features are available in Enterprise edition only:
o Database engine:
o Advanced R integration (parallel and streaming, non-memory bound, processing)
o Standalone R Server
o Polybase head node
o Master Data Services
o Data Quality Services
o Resource Governor
o IO Resource Governor
o Partition Table Parallelism
o NUMA
o Star join query optimizations
o Parallel query processing on partitioned tables and indexes
o Global batch aggregation
o Distributed partitioned views
o Parallel indexed operations
o Auto use of indexed view by query optimizer
o Parallel consistency check
o Utility Control Point
o Analysis Services:
o Scalable shared databases
o Data Mining advanced algorithms
o Perspectives (MOLAP and Tabular)
o Multiple partitions (Tabular)
o Writeback dimensions (MOLAP)
o Proactive caching (MOLAP)
o Direct writeback (MOLAP)
o Measure expressions (MOLAP)
o Push-mode processing (MOLAP)
o DirectQuery storage mode (Tabular)
o Power Pivot for SharePoint integration
o Reporting Services:
o Custom branding
o Data driven report subscription
o Scale our deployment (Web farms)
o Alerting
o Power View
o Mobile BI (Datazen)
18. What are the availability, manageability, and security features in Enterprise Edition only?
* Enterprise edition allows maximum availability, security, and manageability for mission critical database applications.
* These features are available in Enterprise edition only:
o Always On availability groups up to 8 secondary replicas including 2 synchronous secondary replicas (Standard Edition is limited to 1 non-readable secondary)
o Connection director
o Online page and file restore
o Online indexing
o Online schema change
o Fast recovery
o Mirrored backups
o Hot add memory and CPU
o StreamInsight high availability
o Transparent database encryption
o Extensible key management
o Oracle publishing
o Peer to peer transactional replication
o Change Data Capture for Oracle
o Advanced Adapters for Integration Services (e.g. Oracle, Teradata, SAP BW, Analysis Services)
o Advanced Transforms for Integration Services
19. What are the virtualization features in Enterprise Edition only?
Maximum virtualization can be achieved by licensing the entire physical server with Enterprise edition core licenses with Software Assurance (SA) to allow deployment of unlimited number of instances of SQL Server in any number of operating system environment (physical or virtual) and fully utilize hardware computing capacity. This is an ideal solution for private cloud scenario with high virtual machine density, enabling hyper-threading, using dynamic provisioning and de-provisioning of virtual machine resources. Maximum Virtualization will continue to be a Software Assurance benefit that is only available to Enterprise Edition customers.
Source: https://msdn.microsoft.com/en-us/library/bb510411(v=sql.130).aspx#InMemory
In SQL Server 2016 Community Technology Preview 2 (CTP2), improvements to In-Memory OLTP enable scaling to larger databases and higher throughput in order to support bigger workloads. In addition, a number of limitations concerning tables and stored procedures have been removed to make it easier to migrate your applications to and leverage the benefits of In-Memory OLTP.
2 min
Query performance troubleshooting is a super important problem, since
bad performance can happen at any time, and
it can have a big impact on the application performance.
There are a number of different factors that can cause regressions in query performance
The common for all of them is that users want to be able to quickly see what the problem is so they can mitigate it and fix it.
2 min
Row-Level Security (RLS) simplifies the design and coding of security in your application. RLS enables you to implement restrictions on data row access. For example ensuring that workers can access only those data rows that are pertinent to their department, or restricting a customer's data access to only the data relevant to their company.
The access restriction logic is located in the database tier rather than away from the data in another application tier. The database system applies the access restrictions every time that data access is attempted from any tier. This makes your security system more reliable and robust by reducing the surface area of your security system.
Implement RLS by using the CREATE SECURITY POLICY Transact-SQL statement, and predicates created as inline table valued functions.
Limitations during the preview:
RLS is incompatible with database export using Data Tier Application Framework (DACFx). You must drop all RLS policies before exporting.
Security policies cannot target views.
Certain query patterns using OR logic can trigger un-optimized table scans, decreasing query performance.
No syntax highlighting in SQL Server tools.
Source: https://msdn.microsoft.com/en-us/library/mt130841(v=sql.130).aspx
Dynamic data masking limits sensitive data exposure by masking it to non-privileged users. Dynamic data masking helps prevent unauthorized access to sensitive data by enabling customers to designate how much of the sensitive data to reveal with minimal impact on the application layer. It’s a policy-based security feature that hides the sensitive data in the result set of a query over designated database fields, while the data in the database is not changed. Dynamic data masking is easy to use with existing applications, since masking rules are applied in the query results, and there is no need to modify existing queries.
For example, a call center support person may identify callers by several digits of their social security number or credit card number, but those data items should not be fully exposed to the support person. A developer can define a masking rule to be applied to each query result that masks all but the last four digits of any social security number or credit card number in the result set. For another example, by using the appropriate data mask to protect personally identifiable information (PII) data, a developer can query production environments for troubleshooting purposes without violating compliance regulations.
Dynamic data masking limits the exposure of sensitive data and prevents accidental viewing by engineers that access directly databases for troubleshooting purposes or non-privileged application users. Dynamic data masking doesn’t aim to prevent privileged database users from connecting directly to the database and running exhaustive queries that expose pieces of the sensitive data. Dynamic data masking is complimentary to other SQL Server security features (auditing, encryption, row level security…) and it is highly recommended to enable them in addition in order to protect better the sensitive data in the database.
Since data is masked just before being returned to the user, changing the data type to an unmasked type will return unmasked data.
Dynamic data masking is available in SQL Server 2016 Community Technology Preview 2 (CTP2). However, to enable dynamic data masking, you must use trace flags 209 and 219. For Azure SQL Database, see Get started with SQL Database Dynamic Data Masking (Azure Preview portal).
Source: https://msdn.microsoft.com/en-us/library/bb510411(v=sql.130).aspx#highavailability
Load-balancing of read-intent connection requests is now supported across a set of read-only replicas. The previous behavior always directed connections to the first available read-only replica in the routing list. For more information, see Configure load-balancing across read-only replicas.
The number of replicas that support automatic failover has been increased from two to three.
Group Managed Service Accounts are now supported for AlwaysOn Failover Clusters. For more information, see Group Managed Service Accounts. For Windows Server 2012 R2, an update is required to avoid temporary downtime after a password change. To obtain the update, see gMSA-based services can't log on after a password change in a Windows Server 2012 R2 domain.
AlwaysOn Availability Groups supports distributed transactions and the DTC on Windows Server 2016. For more information, see SQL Server 2016 Support for DTC and AlwaysOn Availablity Groups.
You can now configure AlwaysOn Availability Groups to failover when a database goes offline. This change requires the setting the DB_FAILOVER option to ON in the CREATE AVAILABILITY GROUP (Transact-SQL) or ALTER AVAILABILITY GROUP (Transact-SQL) statements.
3 min
2 min
2 min
Capability
Extensible in-database analytics, integrated with R, exposed through T-SQL
Centralized enterprise library for analytic modelsBenefits
No data movement, resulting in faster time to insights
Real-time analytics on transactional data
Integration with existing workflows
Unified governance across analytics and storage
2 min
2 min
One of the key feedback we received was to help you scale Analysis Services to larger data models both Multi-dimensional and Tabular. Tabular models will be able to scale by taking full advantage of high end servers with much higher memory capacity and cores. You will also be able to scale beyond physical memory size with hot data residing in-memory and cold data on disk or SSD. We will also be able to increase throughput with parallel partition processing capability.
MOLAP – multi-dimensional online analytical processing models.
There are separate SQL Server Migration Assistant (SSMA) tools for each of the following databases
Oracle
Sybase
DB2MySQL
Access
With SQL Server 2014, we had four main editions: Enterprise, Business Intelligence, Standard and Express. With SQL Server 2016, we will retire the Business Intelligence edition and consolidate to three main editions. Business Intelligence was created with the SQL Server 2012 release as a way for customers only using Enterprise edition for enterprise BI to continue to take advantage of these capabilities at the EE server price point with the shift of Enterprise edition to only core-based pricing. Uptake on this SKU has been relatively small as most customers have chosen to standard their platform on EE or Standard. ISVs also have wanted to keep their SKU support simple and have not widely adopted this SKU.
For customers who have purchased BI edition to date, there will be transition plans to support access to the right capability set.
For field, more details in the Appendix on the BI server transition. Sellers should follow-up with their LS on specific edition paths. We should NOT disclose any transition paths unless the customer owns BI edition today.
[10/11/2016 9:06 AM] Matthew Burrows:
No Title
Mark R. Murphy
Satya, regarding the announcement that you will release your SQL Server database on the Linux platform, I was wondering if you can walk us through your decision tree just in terms of what you think the potential risks are and what you think the potential rewards are of reaching for that level of openness, if you will. And just how impactful do you think that, that product can be in enhancing Microsoft's share of the database market?
Satya Nadella
Thanks for the question. So the decision logic was driven primarily by what I'd say the increased competitiveness of SQL Server. If you think about where SQL Server now with this new release, SQL Server 2016, it's become a fantastic database for many, many of the workloads, everything from OLTP to data warehousing to BI to advanced analytics. For the Tier 1, this is a capability that's been multiple decades in the work, but here we are with very competitive total cost of ownership, price competitiveness but with a technology that is, in many cases, as Gartner talks about, at the top of the charts when it comes to all of these workloads. So now that we find yourselves with that capability, we're saying, "Look, what's the way to think about market -- all the markets that we can, in fact, take this product to." And the Linux operating system database market is not something that -- which is mostly primarily a Tier 1 segment, is something that we never worked in. And so, therefore, we look at that as an expansion opportunity so we take that. We've already made the call that Azure Linux's FirstClass. We already have 20-plus points of -- or 20-plus percent of VMs in Azure or Linux and we'll all increasingly have Linux via big share of percentage of what is happening in Azure. So for the first time now, we have the ability to go to an enterprise and talk about that entire data estate across Windows and Linux. People don't really move between operating systems. Those choices have been made. But at the same time, now they have a choice around database. And so we think that, that's a very good incremental opportunity for us.
General approach is to scale features down from EE to SE with throttles such that features are programmable in SE but EE is required for scale and performance:
Tabular Models in SE with 16GB memory cap per instance
In-memory OLTP in SE with 64MB memory restriction at the instance level
In-DB-Analytics allow developers to execute RRE-functions outside EE with close-to-RRO limitations (perf & dataset size)
Security, encryption story is fractured: TDE moves from EE to SE; Always Encrypted is EE
Source: https://msdn.microsoft.com/en-us/library/bb522534(v=sql.130).aspx
AlwaysOn Support
Pain Point: There has not been any official Always-On Support for SSIS
Scenario: DB/IT Admin can now easily configure high availability for SSIS catalog DB directly in SSMS, without the need to set it up manually as described in MSDN Blog
Incremental Deployment
Pain Points: Since the SSIS 2012 introduced the “project” concept, developer has to deploy the whole project each time even though they only change part of the project
Scenario: Developer can deploy selected SSIS packages incrementally without deploying the whole project, therefore saving the deployment time
Project Upgrade
Pain Point: During the project upgrade, UX layout or shared connection manager may not be upgraded successfully
Scenario: Developers can upgrade their SSIS 2012/2014 project to the new version of SSIS completely without manual adjustment after upgrade
Source: https://msdn.microsoft.com/en-us/library/bb510411(v=sql.130).aspx
Multiple TempDB Databases
Setup adds multiple tempdb data files during the installation of a new instance. Below are the pertinent details to consider:
By default, setup adds as many tempdb files as the CPU count or 8, whichever is lower.
You can configure the number of tempdb database files using the new command line parameter- /SQLTEMPDBFILECOUNT. It can be used for unattended and interactive installations. setup.exe /Q /ACTION="INSTALL" /IACCEPTSQLSERVERLICENSETERMS /FEATURES="SqlEngine" /INSTANCENAME="SQL15" .. /SQLTEMPDBDIR="D:\tempdb" /SQLTEMPDBFILECOUNT="4" SQLTEMPDBFILECOUNT only accepts an integer value. If the parameter is not given or the value <= 0, setup will use the default value that is the number of (logical) cores on the machine or 8, whichever is lower. If the value is greater than the maximum allowed (cpu count), the installation will fail with an error. Important The SQLTEMPDBFILECOUNT parameter is supported only in the following scenarios or actions: Install, InstallFailoverCluster, CompleteImage (sysprep), CompleteFailoverCluster (sysprep), and RebuildDatabase.
You can configure the number of tempdb database files using the new UI input control on the Database Engine Configuration section.
The primary database file for tempdb will still be tempdb.mdf. The additional tempdb files are named as tempdb_mssql_#.ndf where # where # represents a unique number for each additional tempdb database file created during setup. The purpose of this naming convention is to make them unique. Uninstalling an instance of SQL Server deletes the files with naming convention tempdb_mssql_#.ndf. Do not use tempdb_mssql_*.ndf naming convention for user database files. .
RebuildDatabase scenario deletes system databases and installs them again in clean state. Because the setting of tempdb file count does not persist, the value of number of tempdb files is not known during setup. Therefore, RebuildDatabase scenario does not know the count of tempdb files to be re-added. You can provide the value of the number of tempdb files again with the SQLTEMPDBFILECOUNT parameter. If the parameter is not provided, RebuildDatabase will add a default number of tempdb files, which is as many tempdb files as the CPU count or 8, whichever is lower.
Source: https://msdn.microsoft.com/en-us/library/bb510411(v=sql.130).aspx#TDE
Transparent Data Encryption
Transparent Data Encryption has been enhanced with support for Intel AES-NI hardware acceleration of encryption. This will reduce the CPU overhead of turning on Transparent Data Encryption.
Speaker notes:
This slide shows the evolution of SQL server overtime. Today SQL Server is leader in Database Management System according to Gartner.
Microsoft has made tremendous investments in the platform, in order to make SQL Server 2016 the fastest release ever produced. SQL Server 2016 has been in production in Microsoft Cloud through Azure SQL Database for more than 1 year and now is available to customers and partners to run on-premises or in Service Providers’ datacenter.
Slides features only the core new capabilities in Enterprise (when a comparison with Standard is not needed).
Slides features only the core new capabilities in Standard (when a comparison with Enterprise is not needed).
Complete inventory of features since 2008 R2 by pillar for customers upgrading from SQL Server 2014 (heroes features on earlier slides).
Complete inventory of features since 2008 R2 by pillar for customers upgrading from SQL Server 2012.
Complete inventory of features since 2008 R2 by pillar for customers upgrading from SQL Server 2008 R2.