SlideShare a Scribd company logo

Novedades SQL Server 2014

Download as PPTX, PDF
netmind
netmind

The document outlines the new features and enhancements in Microsoft SQL Server 2014, highlighting the in-memory OLTP engine, which provides high-performance, memory-optimized transaction processing, and new cardinality estimators for improved query execution plans. It emphasizes security enhancements, such as new permissions for greater separation of duties, as well as improvements in the AlwaysOn availability feature, allowing for increased availability and scalability of readable secondary replicas. Additionally, it discusses integration with Azure and modern hardware trends, providing a robust and streamlined database management experience.

Technology
1 of 74
Downloaded 23 times
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
Microsoft SQL Server 2014 NOVEDADES Por Xavier Saladié Julio 2014
Microsoft SQL Server 2014 What’s new? • In-Memory OLTP • New Cardinality Estimator • Security Enhancements • AlwaysOn Enhancements • Resource Governor I/O • Working with Azure
SQL Server 2014 In-Memory OLTP
SQL Server engine In-memory OLTP 4 New high-performance, memory-optimized online transaction processing (OLTP) engine integrated into SQL Server and architected for modern hardware trends Memory-optimized table file group In-Memory OLTP engine: Memory- optimized tables & indexes Native compiled SPs & schema In-Memory OLTP compiler Transaction log Data file group Buffer pool for tables & indexes Lock Manager Proc/plan cache for ad-hoc, T-SQL; interpreter, plans, etc. Parser, catalog, optimizer
Suitable application characteristics 5 • Application is suited for in-memory processing ‐ All performance critical data already fits in memory ‐ Transaction locking or physical latching causing stalls and blocking • Application is “OLTP-Like” ‐ Relatively short-lived transactions ‐ High degree of concurrent transactions from many connections ‐ Examples: Stock trading, travel reservations, order processing • Application porting simplified if ‐ Stored procedures used ‐ Performance problems isolated to subset of tables and SPs
SQL Server integration • Same manageability, administration, and development experience • Integrated queries and transactions • Integrated HA and backup/restore Main-memory optimized • Optimized for in-memory data • Indexes (hash and range) exist only in memory • No buffer pool • Stream-based storage for durability High concurrency • Multiversion optimistic concurrency control with full ACID support • Core engine uses lock-free algorithms • No lock manager, latches, or spinlocks T-SQL compiled to machine code • T-SQL compiled to machine code via C code generator and Visual C compiler • Invoking a procedure is just a DLL entry-point • Aggressive optimizations at compile time Steadily declining memory price, NVRAM Many-core processors Stalling CPU clock rate TCO Hardware trends Business Hybrid engine and integrated experience High-performance data operations Frictionless scale-up Efficient, business-logic processing BenefitsIn-MemoryOLTPTechPillarsDrivers In-memory OLTP architecture
Main-memory optimized • Optimized for in-memory data • Indexes (hash and ordered) exist only in memory • No buffer pool • Stream-based storage for durability Steadily declining memory price, NVRAM Hardware trends Design considerations for memory-optimized tables 7 Table constructs Fixed schema; no ALTER TABLE; must drop/recreate/reload No LOB data types; row size limited to 8,060 No constraints support (primary key only) No identity or calculated columns, or CLR Data and table size considerations Size of tables = (row size * # of rows) Size of hash index = (bucket_count * 8 bytes) Max size SCHEMA_AND_DATA = 512 GB IO for durability SCHEMA_ONLY vs. SCHEMA_AND_DATA Memory-optimized filegroup Data and delta files Transaction log Database recovery High performance data operations BenefitsIn-MemoryOLTPTechPillarsDrivers
Create Table DDL CREATE TABLE [Customer]( [CustomerID] INT NOT NULL PRIMARY KEY NONCLUSTERED HASH WITH (BUCKET_COUNT = 1000000), [Name] NVARCHAR(250) NOT NULL INDEX [IName] HASH WITH (BUCKET_COUNT = 1000000), [CustomerSince] DATETIME NULL ) WITH ( MEMORY_OPTIMIZED = ON, DURABILITY = SCHEMA_AND_DATA); This table is memory optimized This table is durable Secondary indexes are specified inline Hash index
Create Procedure DDL CREATE PROCEDURE [dbo].[InsertOrder] @id INT, @date DATETIME WITH NATIVE_COMPILATION, SCHEMABINDING, EXECUTE AS OWNER AS BEGIN ATOMIC WITH (TRANSACTION ISOLATION LEVEL = SNAPSHOT, LANGUAGE = 'us_english') -- insert T-SQL here END This proc is natively compiled Native procs must be schema-bound Atomic blocks • Create a transaction if there is none • Otherwise, create a savepoint Execution context is required Session settings are fixed at create time
High concurrency • Multiversion optimistic concurrency control with full ACID support • Core engine uses lock- free algorithms • No lock manager, latches, or spinlocks Many-core processors Hardware trends High-concurrency design considerations 10 Impact of no locks or latches Write-write conflict: design application for condition with try.catch Applications dependent on locking; may not be a good candidate Multiple versions of records Increases the memory needed by memory-optimized tables Garbage Collection used to reclaim old versions Transaction scope Support for Isolation Levels: Snapshot, Repeatable Read, Serializable Commit time validation; again must retry logic to deal with failure Frictionless scale-up BenefitsIn-MemoryOLTPTechPillarsDrivers
Example: Write conflict 11 Time Transaction T1 (SNAPSHOT) Transaction T2 (SNAPSHOT) 1 BEGIN 2 BEGIN 3 UPDATE t SET c1=‘bla’ WHERE c2=123 4 UPDATE t SET c1=‘bla’ WHERE c2=123 (write conflict) First writer wins
Guidelines for usage 12 1. Declare isolation level – no locking hints 2. Use retry logic to handle conflicts and validation failures 3. Avoid using long-running transactions
T-SQL compiled to machine code • T-SQL compiled to machine code via C code generator and Visual C compiler • Invoking a procedure is just a DLL entry-point • Aggressive optimizations at compile-time Stalling CPU clock rate Hardware trends Design considerations for native compiled stored procedures 13 Efficient business-logic processing BenefitsIn-MemoryOLTPTechPillarsDrivers Native compiled stored procedures Non-native compilation Performance High. Significantly less instructions to go through No different than T-SQL calls in SQL Server today Migration strategy Application changes; development overhead Easier app migration as can still access memory- optimized tables Access to objects Can only interact with memory-optimized tables All objects; access for transactions across memory optimized and B-tree tables Support for T-SQL constructs Limited T-SQL surface area (limit on memory-optimized interaction) Optimization, stats, and query plan Statistics utilized at CREATE - > Compile time Statistics updates can be used to modify plan at runtime Flexibility Limited (no ALTER procedure, compile-time isolation level) Ad-hoc query patterns
Performance gains 14 In-Memory OLTP Compiler In-Memory OLTP Component Memory-optimized Table Filegroup Data Filegroup SQL Server.exe In-Memory OLTP Engine for Memory_optimized Tables & Indexes TDS Handler and Session Management Natively Compiled SPs and Schema Buffer Pool for Tables & Indexes Proc/Plan cache for ad-hoc T- SQL and SPs Client App Transaction Log Interpreter for TSQL, query plans, expressions Query Interop Access Methods Parser, Catalog, Algebrizer, Optimizer 10-30x more efficient Reduced log bandwidth & contention. Log latency remains Checkpoints are background sequential IO No improvements in communication stack, parameter passing, result set generation Key Existing SQL Component Generated .dll
In-memory data structures 15 Rows • New row format Structure of the row is optimized for memory residency and access • One copy of row Indexes point to rows, they do not duplicate them Indexes • Hash index for point lookups • Memory-optimized nonclustered index for range and ordered scans • Do not exist on disk – recreated during recovery
Memory-optimized table: Row format Key Points • Begin/End timestamp determines row’s validity • No data or index page; just rows • Row size limited to 8060 bytes to allow data to be moved to disk-based table • Not every SQL table schema is supported Row header Payload (table columns) Begin Ts End Ts StmtId IdxLinkCount 8 bytes 8 bytes 4 bytes 2 bytes 8 bytes * (IdxLinkCount – 1)
Key lookup: B-tree vs. memory-optimized table Matching index record Hash index on Name R1 R2 R3 Non-clustered index
OLTP Rocket Science
• No DML triggers • No FOREIGN KEY or CHECK constraints • No IDENTITY columns • 8060 byte hard limit for row length • No UNIQUE indexes other than for the PRIMARY KEY • A maximum of 8 indexes, including the index supporting the PRIMARY KEY • No schema changes are allowed once a table is created (drop/recreate) • Indexes are always and ONLY created at as part of the table creation In-Memory OLTP Limitations
Indexes Comparison for different kinds of operations Operation Memory hash Memory nonclustered Disk Index Scan, retrieve all table rows. Yes Yes Yes Index seek (=). Yes (Full key required.) Yes 1 Yes Index seek (>, <, <=, >=, BETWEEN). No (index scan) Yes 1 Yes Retrieve rows in a sort-order matching the index definition. No Yes Yes Retrieve rows in a sort-order matching the reverse of the index definition. No No Yes
Memory management 21 Data resides in memory at all times • Must configure SQL server with sufficient memory to store memory-optimized tables • Failure to allocate memory will fail transactional workload at run-time • Integrated with SQL Server memory manager and reacts to memory pressure where possible Integration with Resource Governor • “Bind” a database to a resource pool • Mem-opt tables in a database cannot exceed the limit of the resource pool • Hard limit (80% of phys. memory) to ensure system remains stable under memory pressure
Garbage collection 22 Stale Row Versions • Updates, deletes, and aborted insert operations create row versions that (eventually) are no longer visible to any transaction • Slow down scans of index structures • Create unused memory that needs to be reclaimed (i.e. Garbage Collected) Garbage Collection (GC) • Analogous to version store cleanup task for disk-based tables to support Read Committed Snapshot (RCSI) • System maintains ‘oldest active transaction’ hint GC Design • Non-blocking, Cooperative, Efficient, Responsive, Scalable • A dedicated system thread for GC • Active transactions work cooperatively and pick up parts of GC work
Cooperative garbage collection Key Points • Scanners can remove expired rows when found • Offloads work from GC thread • Ensures that frequently visited areas of the index are cleaned regularly • A row needs to be removed from all indexes before memory can be freed • Garbage collection is most efficient if all indexes are frequently accessed 100 200 1 John Smith Kirkland 200 ∞ 1 John Smith Redmond 50 100 1 Jim Spring Kirkland 300 ∞ 1 Ken Stone Boston TX4: Begin = 210 Oldest Active Hint = 175
Durability 24 Memory-optimized tables can be durable or non-durable • Default is ‘durable’ • Non-durable tables are useful for transient data Durable tables are persisted in a single memory-optimized file group Storage used for memory-optimized has a different access pattern than for disk tables File group can have multiple containers (volumes) Additional containers aid in parallel recovery; recovery happens at the speed of IO
On-disk storage 25 Filestream is the underlying storage mechanism Checksums and single-bit correcting ECC on files Data files • ~128MB in size, write 256KB chunks at a time • Stores only the inserted rows (i.e. table content) • Chronologically organized streams of row versions Delta files • File size is not constant, write 4KB chunks at a time. • Stores IDs of deleted rows
Logging for memory-optimized tables 26 Uses SQL transaction log to store content Each log record contains a log record header followed by opaque memory optimized-specific log content All logging for memory-optimized tables is logical • No log records for physical structure modifications. • No index-specific / index-maintenance log records. • No UNDO information is logged Recovery Models All three recovery models are supported
Backup for memory-optimized tables 27 Integrated with SQL Database Backup • Memory-Optimized file group is backed up as part SQL Server database backup • Existing backup scripts work with minimal or no changes • Transaction log backup includes memory-optimized log records Not supported Differential backup
Recovery for memory-optimized tables 28 Analysis Phase Finds the last completed checkpoint Data Load • Load from set of data/delta files from the last completed checkpoint • Parallel Load by reading data/delta files using 1 thread / file Redo phase to apply tail of the log • Apply the transaction log from last checkpoint • Concurrent with REDO on disk-based tables No UNDO phase for memory-optimized tables Only committed transactions are logged
Myth #1 Reality SQL Server In-Memory OLTP is a recent response to competitors’ offerings
Myth #2 Reality In-Memory OLTP is like DBCC PINTABLE
Myth #3 Reality In-Memory Databases are new separate products
Myth #4 Reality You can use In-Memory OLTP in an existing SQL Server app with NO changes whatsoever
Myth #5 Reality Since tables are in memory, the data is not Durable or Highly Available – I will lose it after server crash
Demo In-Memory Tables Performance
In-memory OLTP summary 35 What’s being delivered • High-performance, memory-optimized OLTP engine integrated into SQL Server and architected for modern hardware trends Main benefits • Optimized for in-memory data up to 20–30 times throughput ‐ Indexes (hash and range) exist only in memory; no buffer pool, B-trees ‐ T-SQL compiled to machine code via C code generator and Visual C compiler ‐ Core engine uses lock-free algorithms; no lock manager, latches, or spinlocks • Multiversion optimistic concurrency control with full ACID support • On-ramp existing applications • Integrated experience with same manageability, administration, and development experience
SQL Server 2014 Cardinality Enhancements
Cardinality 37 • Execution Plans uses Cardinality in order to get an estimation of number of rows for each query • Although the new cardinality still works based on Statistics the algorithm has been dramatically changed • Databases in native compatibility level (120) works with the new estimator version • Change that behavior with the OPTION (QUERYTRACEON 9481) to still be executed with the old version (per Query basis) • Databases in compatibility level 110 could be executed with the new version when using QUERYTRACEON 2312 hint (per Query basis)
Scenarios 38 • New cardinality estimates use an average cardinality for recently added ascending data (ascending key problem) without Statistics Update ‐ Old Version estimates 0 rows ‐ New Version uses average cardinality • New cardinality estimates assume filtered predicates on the same table have some correlation ‐ Old and New Version depends on the specific sample • New cardinality estimates assume filtered predicates on different tables are independent ‐ Old and New Version depends on the specific sample
39 • Check the performance of your workloads and do the math ‐ Compatibility Level 110 ‐ Compatibility Level 110 and add OPTION (QUERYTRACEON 2312) to some querys ‐ Native Compatibility Level (120) ‐ Native Compatibility Level (120) and add OPTION (QUERYTRACEON 9481) to some querys Suggestions
Demo Cardinality
SQL Server 2014 Security Enhancements
Separation of duties enhancement • Four new permissions ‐ CONNECT ANY DATABASE (server scope) ‐ IMPERSONATE ANY LOGIN (server scope) ‐ SELECT ALL USER SECURABLES (server scope) ‐ ALTER ANY DATABASE EVEN SESSION (database scope) • Main benefit ‐ Greater role separation to restrict multiple DBA roles ‐ Ability to create new roles for database administrators who are not sysadmin (super user) ‐ Ability to create new roles for users or apps with specific purposes
Best practices for separation of duties • Eliminate the use of superusers (SA login, SYSADMIN server role, DBO database user) • Use permission system rather than superuser • Use CONTROL SERVER (server level) and CONTROL DATABASE (database level) instead and use DENY for specifics • Always document the user of ownership chains
Backup encryption • Increase security of backups stored separate from the instance (another environment such as the Cloud) • Encryption keys can be stored on-premises while backup files in the cloud • Support non-encrypted databases (don’t need to turn on Transparent Data Encryption anymore) • Different policies for databases and their backups
T-SQL BACKUP / RESTORE BACKUP DATABASE <dbname> TO <device> = <path to device> WITH ENCRYPTION ( ALGORITHM = <Algorithm_name> , { SERVER CERTIFICATE = <Encryptor_Name> | SERVER ASYMMETRIC KEY = <Encryptor_Name> } ); No changes to RESTORE
T-SQL views • msdb.dbo.backupset • msdb.dbo.backupmediaset backup_set_id name key_algorithm encryptor_thumbprint encryptor_type 3 Full Backup NULL NULL NULL 4 Full Backup aes_256 0x00B1BD62DAA0196 CERTIFICATE media_set_id is_password_protected is_compressed is_encrypted 3 0 1 0 4 0 1 1
Additional details • AES 128, AES 192, AES 256, and Triple DES • Unique backup key is generated for each backup • Certificate • Asymmetric key from an EKM provider only • All operations require certificate or key • Appended backup is not supported • Compression has no effect on pre-encrypted databases
SQL Server 2014 AlwaysOn Enhancements
AlwaysOn in SQL Server 2014 • What’s being delivered • Increase number of secondaries from four to eight • Increase availability of readable secondaries • Support for Windows Server 2012 CSV • Enhanced diagnostics • Main benefits • Further scale out read workloads across (possibly geo-distributed) replicas • Use readable secondaries despite network failures (important in geo-distributed environments) • Improve SAN storage utilization • Avoid drive letter limitation (max 24 drives) via CSV paths • Increase resiliency of storage failover • Ease troubleshooting
Description • Increase number of secondaries (4–8) • Max number of sync secondaries is still two Increase number of Availability Group secondaries Reason • Customers want to use readable secondaries • One technology to configure and manage • Many times faster than replication • Customers are asking for more database replicas (4–8) • To reduce query latency (large-scale environments) • To scale out read workloads
Description Allow FCI customers to configure CSV paths for system and user databases Support for Windows Server Cluster Shared Volumes Reason • Avoid drive letter limitation on SAN (max 24 drives) • Improves SAN storage utilization and management • Increased resiliency of storage failover (abstraction of temporary disk-level failures) • Migration of SQL Server customers using PolyServe (to be discontinued in 2013)
Description Allow FCI customers to configure CSV paths for system and user databases Support for Windows Server Cluster Shared Volumes Reason • Avoid drive letter limitation on SAN (max 24 drives) • Improves SAN storage utilization and management • Increased resiliency of storage failover (abstraction of temporary disk-level failures) • Migration of SQL Server customers using PolyServe (to be discontinued in 2013)
SQL Server 2014 Resource Governor with IO
Resource Governor goals • Ability to differentiate workloads • Ability to monitor resource usage per group • Limit controls to enable throttled execution or prevent/minimize probability of “run-aways” • Prioritize workloads • Provide predictable execution of workloads • Specify resource boundaries between workloads
Resource Governor components
Complete resource governance • What’s being delivered ‐ Add max/min IOPS per volume to Resource Governor pools ‐ Add DMVs and perfcounters for IO statistics per pool per volume ‐ Update SSMS Intellisense for new T-SQL ‐ Update SMO and DOM for new T-SQL and objects • Main benefits ‐ Better isolation (CPU, memory, and IO) for multitenant workloads ‐ Guarantee performance in private cloud and hosters scenario
Resource pools • Represents physical resources of server • Can have one or more workloads assigned to pool • Pool divided into shared and non-shared • Pools control min/max for CPU/memory and now IOPS CREATE RESOURCE POOL pool_name [ WITH ( [ MIN_CPU_PERCENT = value ] [ [ , ] MAX_CPU_PERCENT = value ] [ [ , ] CAP_CPU_PERCENT = value ] [ [ , ] AFFINITY {SCHEDULER = AUTO | (Scheduler_range_spec) | NUMANODE = (NUMA_node_range_spec)} ] [ [ , ] MIN_MEMORY_PERCENT = value ] [ [ , ] MAX_MEMORY_PERCENT = value ] [ [ , ] MIN_IOPS_PER_VOLUME = value ] [ [ , ] MAX_IOPS_PER_VOLUME = value ]) ]
Resource pools • Minimums across all resource pools can not exceed 100 percent • Non-shared portion provides minimums • Shared portion provides maximums • Pools can define min/max for CPU/Memory/IOPS ‐ Mins defined non-shared ‐ Max defined shared
Steps to implement Resource Governor • Create workload groups • Create function to classify requests into workload group • Register the classification function in the previous step with the Resource Governor • Enable Resource Governor • Monitor resource consumption for each workload group • Use monitor to establish pools • Assign workload group to pool
Resource Governor scenarios • Scenario 1: I just got a new version of SQL Server and would like to make use of resource governor. How can I use it in my environment? • Scenario 2 (based on Scenario 1): Based on monitoring results I would like to see an event any time a query in the ad-hoc group (groupAdhoc) runs longer than 30 seconds. • Scenario 3 (based on Scenario 2): I want to further restrict the ad-hoc group so it does not exceed 50 percent of CPU usage when all requests are cumulated.
Monitoring Resource Governor • System views ‐ sys.resource_governor_resource_pools ‐ sys.resource_governor_configuration • DMVs ‐ sys.dm_resource_governor_resource_pools ‐ sys.dm_resource_governor_resource_pool_volumes ‐ sys.dm_resource_governor_configuration • New performance counters ‐ SQL Server:Resource Pool Stats ‐ SQL Server:Workload group • XEvents ‐ file_read_enqueued ‐ file_write_enqueued
SQL Server 2014 Backup to Cloud
Backup to Windows Azure What’s being delivered • SQL Server supports backups to and restores from the Windows Azure Blob storage service (UI, T-SQL, PowerShell commandlets) Main benefit: Take advantage of Windows Azure Blob storage • Flexible, reliable (3-copies geo-DR), and limitless off-site storage • No need of backup media management • No overhead of hardware management CREATE CREDENTIAL mystoragecred WITH IDENTITY = ‘mystorage', SECRET = ‘<your storage access key> BACKUP DATABASE mydb TO URL ='https://mystorage.blob.core.windows.net/backup-container/mydb- 20130411.bak' WITH CREDENTIAL = ‘mystoragecred', FORMAT, COMPRESSION, STATS = 5, MEDIANAME = ‘mydb backup 20130411', MEDIADESCRIPTION = 'Backup of mydb'
Backup to Windows Azure Windows Azure storage WA WindowsAzure Blobs • On-site/off-site storage costs • Device management costs Box • XDrives limited to 1 terabyte • Max 16 drives • Manage drives and policy • Near “bottomless” storage • Off-site, geo-redundant • No provisioning • No device management • Media safety (decay-free) • Remote accessibility
Backup to Windows Azure • Simple configuration UI • Easy creation of Azure credential • No overhead
Backup to Windows Azure Tool • What is it? ‐ Stand-alone Tool that adds backup to Windows Azure capabilities and backup encryption to prior versions of SQL Server • Benefits ‐ One Cloud Backup strategy across prior versions of SQL Server including 2005, 2008, and 2008 R2 ‐ Adds backup encryption to prior versions, locally or in the cloud ‐ Takes advantage of backup to Azure ‐ Easy configuration
Managed backup to Azure • What’s being delivered ‐ Agent that manages and automates SQL Server backup policy • Main benefit ‐ Large-scale management and no need to manage backup policy  Context-aware – for example, workload/throttling  Minimal knobs – control retention period  Manage whole instance or particular databases ‐ Take advantage of backup to Azure  Inherently off-site  Geo-redundant  Minimal storage costs  Zero hardware management Example: EXEC smart_admin.sp_set_db_backup @database_name='TestDB', @storage_url=<storage url>, @retention_days=30, @credential_name='MyCredential', @enable_backup=1
SQL Server 2014 Database Data and Log Files in Azure Storage
SQL Server data and log files in Windows Azure storage • What’s being delivered ‐ Ability to move data and log files in Windows Azure Storage, while keeping the compute node of SQL Server on-premises ‐ Transparent Data Encryption (TDE) is supported • Main benefits ‐ No application changes required ‐ Centralized copy of data and log files ‐ Enjoy unlimited storage capacity in Azure Storage (built in HA, SLA, geo-DR) ‐ Secure because TDE encryption key can be stored on-premises ‐ Restore database is simply an attach operation
SQL Server data and log files in Windows Azure storage
SQL Server 2014 Deploy Database to Windows Azure Wizard
Easy on-ramp to cloud
Deploy databases to Windows Azure VM • What’s being delivered ‐ New wizard to deploy databases to SQL Server in Windows Azure VM ‐ Can also create a new Windows Azure VM if needed • Main benefits ‐ Easy to use  Perfect for database administrators new to Azure and for ad hoc scenarios ‐ Complexity hidden  Detailed Azure knowledge not needed  Almost no overhead: defining factor for time-to-transfer is database size
Call to action • Download Trial SQL Server 2014 http://technet.microsoft.com/en-US/evalcenter/dn205290.aspx • Trial Azure http://azure.microsoft.com/en-us/pricing/free-trial/ • SQL Server http://www.microsoft.com/SQLServer

More Related Content

What's hot (20)

PPTX
SQL Explore 2012: P&T Part 2
sqlserver.co.il
 
PDF
SQL Server 2019 CTP2.4
Gianluca Hotz
 
PPTX
SQL Server 2014 New Features (Sql Server 2014 Yenilikleri)
BT Akademi
 
PDF
MySQL Tuning
Ford AntiTrust
 
PDF
Always on in sql server 2017
Gianluca Hotz
 
PDF
MySQL 5.6 Performance
MYXPLAIN
 
PDF
MySQL Performance Tuning Variables
FromDual GmbH
 
PPTX
My sql performance tuning course
Alberto Centanni
 
PPTX
SQL Explore 2012: P&T Part 3
sqlserver.co.il
 
PDF
MySQL Performance - Best practices
Ted Wennmark
 
PPTX
SQL 2014 In-Memory OLTP
Amber Keyse
 
PDF
SQL Server Best Practices - Install SQL Server like a boss (RELOADED)
Andre Essing
 
PPT
MySQL Performance Tuning at COSCUP 2014
Ryusuke Kajiyama
 
PDF
MariaDB Server Performance Tuning & Optimization
MariaDB plc
 
PPTX
Brk2051 sql server on linux and docker
Bob Ward
 
PDF
01 upgrade to my sql8
Ted Wennmark
 
PDF
The InnoDB Storage Engine for MySQL
Morgan Tocker
 
PDF
Introducing the ultimate MariaDB cloud, SkySQL
MariaDB plc
 
PDF
Evolution of DBA in the Cloud Era
Mydbops
 
PDF
Remote DBA Experts SQL Server 2008 New Features
Remote DBA Experts
 
SQL Explore 2012: P&T Part 2
sqlserver.co.il
 
SQL Server 2019 CTP2.4
Gianluca Hotz
 
SQL Server 2014 New Features (Sql Server 2014 Yenilikleri)
BT Akademi
 
MySQL Tuning
Ford AntiTrust
 
Always on in sql server 2017
Gianluca Hotz
 
MySQL 5.6 Performance
MYXPLAIN
 
MySQL Performance Tuning Variables
FromDual GmbH
 
My sql performance tuning course
Alberto Centanni
 
SQL Explore 2012: P&T Part 3
sqlserver.co.il
 
MySQL Performance - Best practices
Ted Wennmark
 
SQL 2014 In-Memory OLTP
Amber Keyse
 
SQL Server Best Practices - Install SQL Server like a boss (RELOADED)
Andre Essing
 
MySQL Performance Tuning at COSCUP 2014
Ryusuke Kajiyama
 
MariaDB Server Performance Tuning & Optimization
MariaDB plc
 
Brk2051 sql server on linux and docker
Bob Ward
 
01 upgrade to my sql8
Ted Wennmark
 
The InnoDB Storage Engine for MySQL
Morgan Tocker
 
Introducing the ultimate MariaDB cloud, SkySQL
MariaDB plc
 
Evolution of DBA in the Cloud Era
Mydbops
 
Remote DBA Experts SQL Server 2008 New Features
Remote DBA Experts
 

Viewers also liked (20)

PDF
netmind: Certificaciones PMI
netmind
 
PDF
¿Es cara la arquitectura empresarial?
Matersys
 
PDF
netmind - Introducción al Business Analysis
netmind
 
PDF
Certificaciones en Gestión de Proyectos
netmind
 
PDF
Tendencias TIC: Seminario de netmind para Orange
netmind
 
PDF
Tendencias en la Economía Digital: Big Data, Cloud y Movilidad
netmind
 
PDF
Certificaciones Profesionales TIC
netmind
 
PDF
Transición a Proyectos Ágiles - netmind
netmind
 
PDF
Seminario Business Analysis - La conexión entre negocio y equipo tecnológico
netmind
 
PDF
Gigatic 2015 - Digital business through it people
netmind
 
PDF
Gestión basada en Metodologías Ágiles
netmind
 
PDF
Arquitectura Empresarial
BOC Ibérica
 
PDF
Project Management & Business Analysis
netmind
 
PDF
Tech tuesday Big data with horton works
netmind
 
PDF
Gic vista desde los procesos de negocio
Marta Silvia Tabares
 
PPTX
Novedades en Windows Server 2012 R2
netmind
 
PDF
NETMIND - Catálogo de Formación 2014 -2015
netmind
 
PDF
Alineación del departamento de TI con el negocio
netmind
 
PDF
Techtuesday Arquitectura Empresarial
netmind
 
PDF
Uml for IT Business Analyst a practical guide
Ricardo Quezada Rey
 
netmind: Certificaciones PMI
netmind
 
¿Es cara la arquitectura empresarial?
Matersys
 
netmind - Introducción al Business Analysis
netmind
 
Certificaciones en Gestión de Proyectos
netmind
 
Tendencias TIC: Seminario de netmind para Orange
netmind
 
Tendencias en la Economía Digital: Big Data, Cloud y Movilidad
netmind
 
Certificaciones Profesionales TIC
netmind
 
Transición a Proyectos Ágiles - netmind
netmind
 
Seminario Business Analysis - La conexión entre negocio y equipo tecnológico
netmind
 
Gigatic 2015 - Digital business through it people
netmind
 
Gestión basada en Metodologías Ágiles
netmind
 
Arquitectura Empresarial
BOC Ibérica
 
Project Management & Business Analysis
netmind
 
Tech tuesday Big data with horton works
netmind
 
Gic vista desde los procesos de negocio
Marta Silvia Tabares
 
Novedades en Windows Server 2012 R2
netmind
 
NETMIND - Catálogo de Formación 2014 -2015
netmind
 
Alineación del departamento de TI con el negocio
netmind
 
Techtuesday Arquitectura Empresarial
netmind
 
Uml for IT Business Analyst a practical guide
Ricardo Quezada Rey
 
Ad

Similar to Novedades SQL Server 2014 (20)

PDF
SQL Server 2014 Mission Critical Performance - Level 300 Presentation
David J Rosenthal
 
POTX
Business Insight 2014 - Microsofts nye BI og database platform - Erling Skaal...
Microsoft
 
PPTX
SQL Server In-Memory OLTP: What Every SQL Professional Should Know
Bob Ward
 
PPTX
Hekaton introduction for .Net developers
Shy Engelberg
 
PDF
In-memory ColumnStore Index
SolidQ
 
PDF
Best Practices – Extreme Performance with Data Warehousing on Oracle Databa...
Edgar Alejandro Villegas
 
PPTX
Geek Sync I Need for Speed: In-Memory Databases in Oracle and SQL Server
IDERA Software
 
PDF
Oracle DB In-Memory technologie v kombinaci s procesorem M7
MarketingArrowECS_CZ
 
PPTX
Best storage engine for MySQL
tomflemingh2
 
PPTX
An introduction to column store indexes and batch mode
Chris Adkin
 
PPTX
Jss 2015 in memory and operational analytics
David Barbarin
 
PPTX
[JSS2015] In memory and operational analytics
GUSS
 
PPTX
SQL Server 2014 Memory Optimised Tables - Advanced
Tony Rogerson
 
PPTX
MemSQL 201: Advanced Tips and Tricks Webcast
SingleStore
 
PPTX
MySQL: Know more about open Source Database
Mahesh Salaria
 
PPTX
Hekaton (xtp) introduction
Tara Shankar Jana
 
PDF
Columnstore indexes in sql server 2014
Antonios Chatzipavlis
 
PPTX
Cassandra training
András Fehér
 
PDF
Dynamics ax performance tuning
OutsourceAX
 
PPT
ORACLE 12C-New-Features
Navneet Upneja
 
SQL Server 2014 Mission Critical Performance - Level 300 Presentation
David J Rosenthal
 
Business Insight 2014 - Microsofts nye BI og database platform - Erling Skaal...
Microsoft
 
SQL Server In-Memory OLTP: What Every SQL Professional Should Know
Bob Ward
 
Hekaton introduction for .Net developers
Shy Engelberg
 
In-memory ColumnStore Index
SolidQ
 
Best Practices – Extreme Performance with Data Warehousing on Oracle Databa...
Edgar Alejandro Villegas
 
Geek Sync I Need for Speed: In-Memory Databases in Oracle and SQL Server
IDERA Software
 
Oracle DB In-Memory technologie v kombinaci s procesorem M7
MarketingArrowECS_CZ
 
Best storage engine for MySQL
tomflemingh2
 
An introduction to column store indexes and batch mode
Chris Adkin
 
Jss 2015 in memory and operational analytics
David Barbarin
 
[JSS2015] In memory and operational analytics
GUSS
 
SQL Server 2014 Memory Optimised Tables - Advanced
Tony Rogerson
 
MemSQL 201: Advanced Tips and Tricks Webcast
SingleStore
 
MySQL: Know more about open Source Database
Mahesh Salaria
 
Hekaton (xtp) introduction
Tara Shankar Jana
 
Columnstore indexes in sql server 2014
Antonios Chatzipavlis
 
Cassandra training
András Fehér
 
Dynamics ax performance tuning
OutsourceAX
 
ORACLE 12C-New-Features
Navneet Upneja
 
Ad

More from netmind (20)

PDF
Kanban Method Lean Kanban University
netmind
 
PDF
DSDM Frameworks for Agile Project Management Offices
netmind
 
PDF
Team Kanban Practitioner
netmind
 
PDF
KMP I: Kanban System Design
netmind
 
PPTX
DASA Meetup Madrid 2018
netmind
 
PPTX
Escape from Earth en PMI ® EMEA 2018
netmind
 
PPTX
Las 5 claves de la gamificación en el aprendizaje de COBIT®
netmind
 
PPTX
DevOps - Certificación oficial DASA
netmind
 
PPTX
Comunidades de Práctica
netmind
 
PPTX
PMBOK® 6ª edición NOVEDADES
netmind
 
PPTX
CERTIFICACIONES PMI®
netmind
 
PPTX
Seminario Tendencias en Gestión de Proyectos
netmind
 
PPTX
MSP Managing Successful Programmes
netmind
 
PPTX
MoP - Management of Portfolios
netmind
 
PDF
Foundations of the Scaled Agile Framework® (SAFe® ) 4.5
netmind
 
PDF
Management 3.0
netmind
 
PPTX
Arquitectura de Empresa TOGAF
netmind
 
PDF
CAS 2017 Miquel Rodríguez - Taller Training from the BACK of the Room
netmind
 
PPTX
CAS 2017 Aleix Palau - Peer Learning Universities. Aprendiendo de los desafío...
netmind
 
PDF
CAS 2017 Alfred Maeso - Business Analysis: Superpoderes para el Product Owner
netmind
 
Kanban Method Lean Kanban University
netmind
 
DSDM Frameworks for Agile Project Management Offices
netmind
 
Team Kanban Practitioner
netmind
 
KMP I: Kanban System Design
netmind
 
DASA Meetup Madrid 2018
netmind
 
Escape from Earth en PMI ® EMEA 2018
netmind
 
Las 5 claves de la gamificación en el aprendizaje de COBIT®
netmind
 
DevOps - Certificación oficial DASA
netmind
 
Comunidades de Práctica
netmind
 
PMBOK® 6ª edición NOVEDADES
netmind
 
CERTIFICACIONES PMI®
netmind
 
Seminario Tendencias en Gestión de Proyectos
netmind
 
MSP Managing Successful Programmes
netmind
 
MoP - Management of Portfolios
netmind
 
Foundations of the Scaled Agile Framework® (SAFe® ) 4.5
netmind
 
Management 3.0
netmind
 
Arquitectura de Empresa TOGAF
netmind
 
CAS 2017 Miquel Rodríguez - Taller Training from the BACK of the Room
netmind
 
CAS 2017 Aleix Palau - Peer Learning Universities. Aprendiendo de los desafío...
netmind
 
CAS 2017 Alfred Maeso - Business Analysis: Superpoderes para el Product Owner
netmind
 

Recently uploaded (20)

PDF
New from BookNet Canada for 2025: BNC BiblioShare - Tech Forum 2025
BookNet Canada
 
PDF
Exolore The Essential AI Tools in 2025.pdf
Srinivasan M
 
PDF
Agentic AI lifecycle for Enterprise Hyper-Automation
Debmalya Biswas
 
PDF
Mastering Financial Management in Direct Selling
Epixel MLM Software
 
PDF
From Code to Challenge: Crafting Skill-Based Games That Engage and Reward
aiyshauae
 
PDF
CIFDAQ Market Insights for July 7th 2025
CIFDAQ
 
PDF
CIFDAQ Market Wrap for the week of 4th July 2025
CIFDAQ
 
PDF
Using FME to Develop Self-Service CAD Applications for a Major UK Police Force
Safe Software
 
PDF
POV_ Why Enterprises Need to Find Value in ZERO.pdf
darshakparmar
 
PDF
Empower Inclusion Through Accessible Java Applications
Ana-Maria Mihalceanu
 
PPTX
From Sci-Fi to Reality: Exploring AI Evolution
Svetlana Meissner
 
PDF
[Newgen] NewgenONE Marvin Brochure 1.pdf
darshakparmar
 
PDF
IoT-Powered Industrial Transformation – Smart Manufacturing to Connected Heal...
Rejig Digital
 
PDF
How Startups Are Growing Faster with App Developers in Australia.pdf
India App Developer
 
PDF
Bitcoin for Millennials podcast with Bram, Power Laws of Bitcoin
Stephen Perrenod
 
PDF
Newgen Beyond Frankenstein_Build vs Buy_Digital_version.pdf
darshakparmar
 
PDF
Fl Studio 24.2.2 Build 4597 Crack for Windows Free Download 2025
faizk77g
 
PDF
Chris Elwell Woburn, MA - Passionate About IT Innovation
Chris Elwell Woburn, MA
 
PPTX
Webinar: Introduction to LF Energy EVerest
DanBrown980551
 
PDF
The Rise of AI and IoT in Mobile App Tech.pdf
IMG Global Infotech
 
New from BookNet Canada for 2025: BNC BiblioShare - Tech Forum 2025
BookNet Canada
 
Exolore The Essential AI Tools in 2025.pdf
Srinivasan M
 
Agentic AI lifecycle for Enterprise Hyper-Automation
Debmalya Biswas
 
Mastering Financial Management in Direct Selling
Epixel MLM Software
 
From Code to Challenge: Crafting Skill-Based Games That Engage and Reward
aiyshauae
 
CIFDAQ Market Insights for July 7th 2025
CIFDAQ
 
CIFDAQ Market Wrap for the week of 4th July 2025
CIFDAQ
 
Using FME to Develop Self-Service CAD Applications for a Major UK Police Force
Safe Software
 
POV_ Why Enterprises Need to Find Value in ZERO.pdf
darshakparmar
 
Empower Inclusion Through Accessible Java Applications
Ana-Maria Mihalceanu
 
From Sci-Fi to Reality: Exploring AI Evolution
Svetlana Meissner
 
[Newgen] NewgenONE Marvin Brochure 1.pdf
darshakparmar
 
IoT-Powered Industrial Transformation – Smart Manufacturing to Connected Heal...
Rejig Digital
 
How Startups Are Growing Faster with App Developers in Australia.pdf
India App Developer
 
Bitcoin for Millennials podcast with Bram, Power Laws of Bitcoin
Stephen Perrenod
 
Newgen Beyond Frankenstein_Build vs Buy_Digital_version.pdf
darshakparmar
 
Fl Studio 24.2.2 Build 4597 Crack for Windows Free Download 2025
faizk77g
 
Chris Elwell Woburn, MA - Passionate About IT Innovation
Chris Elwell Woburn, MA
 
Webinar: Introduction to LF Energy EVerest
DanBrown980551
 
The Rise of AI and IoT in Mobile App Tech.pdf
IMG Global Infotech
 

Novedades SQL Server 2014

  • 1. Microsoft SQL Server 2014 NOVEDADES Por Xavier Saladié Julio 2014
  • 2. Microsoft SQL Server 2014 What’s new? • In-Memory OLTP • New Cardinality Estimator • Security Enhancements • AlwaysOn Enhancements • Resource Governor I/O • Working with Azure
  • 4. SQL Server engine In-memory OLTP 4 New high-performance, memory-optimized online transaction processing (OLTP) engine integrated into SQL Server and architected for modern hardware trends Memory-optimized table file group In-Memory OLTP engine: Memory- optimized tables & indexes Native compiled SPs & schema In-Memory OLTP compiler Transaction log Data file group Buffer pool for tables & indexes Lock Manager Proc/plan cache for ad-hoc, T-SQL; interpreter, plans, etc. Parser, catalog, optimizer
  • 5. Suitable application characteristics 5 • Application is suited for in-memory processing ‐ All performance critical data already fits in memory ‐ Transaction locking or physical latching causing stalls and blocking • Application is “OLTP-Like” ‐ Relatively short-lived transactions ‐ High degree of concurrent transactions from many connections ‐ Examples: Stock trading, travel reservations, order processing • Application porting simplified if ‐ Stored procedures used ‐ Performance problems isolated to subset of tables and SPs
  • 6. SQL Server integration • Same manageability, administration, and development experience • Integrated queries and transactions • Integrated HA and backup/restore Main-memory optimized • Optimized for in-memory data • Indexes (hash and range) exist only in memory • No buffer pool • Stream-based storage for durability High concurrency • Multiversion optimistic concurrency control with full ACID support • Core engine uses lock-free algorithms • No lock manager, latches, or spinlocks T-SQL compiled to machine code • T-SQL compiled to machine code via C code generator and Visual C compiler • Invoking a procedure is just a DLL entry-point • Aggressive optimizations at compile time Steadily declining memory price, NVRAM Many-core processors Stalling CPU clock rate TCO Hardware trends Business Hybrid engine and integrated experience High-performance data operations Frictionless scale-up Efficient, business-logic processing BenefitsIn-MemoryOLTPTechPillarsDrivers In-memory OLTP architecture
  • 7. Main-memory optimized • Optimized for in-memory data • Indexes (hash and ordered) exist only in memory • No buffer pool • Stream-based storage for durability Steadily declining memory price, NVRAM Hardware trends Design considerations for memory-optimized tables 7 Table constructs Fixed schema; no ALTER TABLE; must drop/recreate/reload No LOB data types; row size limited to 8,060 No constraints support (primary key only) No identity or calculated columns, or CLR Data and table size considerations Size of tables = (row size * # of rows) Size of hash index = (bucket_count * 8 bytes) Max size SCHEMA_AND_DATA = 512 GB IO for durability SCHEMA_ONLY vs. SCHEMA_AND_DATA Memory-optimized filegroup Data and delta files Transaction log Database recovery High performance data operations BenefitsIn-MemoryOLTPTechPillarsDrivers
  • 8. Create Table DDL CREATE TABLE [Customer]( [CustomerID] INT NOT NULL PRIMARY KEY NONCLUSTERED HASH WITH (BUCKET_COUNT = 1000000), [Name] NVARCHAR(250) NOT NULL INDEX [IName] HASH WITH (BUCKET_COUNT = 1000000), [CustomerSince] DATETIME NULL ) WITH ( MEMORY_OPTIMIZED = ON, DURABILITY = SCHEMA_AND_DATA); This table is memory optimized This table is durable Secondary indexes are specified inline Hash index
  • 9. Create Procedure DDL CREATE PROCEDURE [dbo].[InsertOrder] @id INT, @date DATETIME WITH NATIVE_COMPILATION, SCHEMABINDING, EXECUTE AS OWNER AS BEGIN ATOMIC WITH (TRANSACTION ISOLATION LEVEL = SNAPSHOT, LANGUAGE = 'us_english') -- insert T-SQL here END This proc is natively compiled Native procs must be schema-bound Atomic blocks • Create a transaction if there is none • Otherwise, create a savepoint Execution context is required Session settings are fixed at create time
  • 10. High concurrency • Multiversion optimistic concurrency control with full ACID support • Core engine uses lock- free algorithms • No lock manager, latches, or spinlocks Many-core processors Hardware trends High-concurrency design considerations 10 Impact of no locks or latches Write-write conflict: design application for condition with try.catch Applications dependent on locking; may not be a good candidate Multiple versions of records Increases the memory needed by memory-optimized tables Garbage Collection used to reclaim old versions Transaction scope Support for Isolation Levels: Snapshot, Repeatable Read, Serializable Commit time validation; again must retry logic to deal with failure Frictionless scale-up BenefitsIn-MemoryOLTPTechPillarsDrivers
  • 11. Example: Write conflict 11 Time Transaction T1 (SNAPSHOT) Transaction T2 (SNAPSHOT) 1 BEGIN 2 BEGIN 3 UPDATE t SET c1=‘bla’ WHERE c2=123 4 UPDATE t SET c1=‘bla’ WHERE c2=123 (write conflict) First writer wins
  • 12. Guidelines for usage 12 1. Declare isolation level – no locking hints 2. Use retry logic to handle conflicts and validation failures 3. Avoid using long-running transactions
  • 13. T-SQL compiled to machine code • T-SQL compiled to machine code via C code generator and Visual C compiler • Invoking a procedure is just a DLL entry-point • Aggressive optimizations at compile-time Stalling CPU clock rate Hardware trends Design considerations for native compiled stored procedures 13 Efficient business-logic processing BenefitsIn-MemoryOLTPTechPillarsDrivers Native compiled stored procedures Non-native compilation Performance High. Significantly less instructions to go through No different than T-SQL calls in SQL Server today Migration strategy Application changes; development overhead Easier app migration as can still access memory- optimized tables Access to objects Can only interact with memory-optimized tables All objects; access for transactions across memory optimized and B-tree tables Support for T-SQL constructs Limited T-SQL surface area (limit on memory-optimized interaction) Optimization, stats, and query plan Statistics utilized at CREATE - > Compile time Statistics updates can be used to modify plan at runtime Flexibility Limited (no ALTER procedure, compile-time isolation level) Ad-hoc query patterns
  • 14. Performance gains 14 In-Memory OLTP Compiler In-Memory OLTP Component Memory-optimized Table Filegroup Data Filegroup SQL Server.exe In-Memory OLTP Engine for Memory_optimized Tables & Indexes TDS Handler and Session Management Natively Compiled SPs and Schema Buffer Pool for Tables & Indexes Proc/Plan cache for ad-hoc T- SQL and SPs Client App Transaction Log Interpreter for TSQL, query plans, expressions Query Interop Access Methods Parser, Catalog, Algebrizer, Optimizer 10-30x more efficient Reduced log bandwidth & contention. Log latency remains Checkpoints are background sequential IO No improvements in communication stack, parameter passing, result set generation Key Existing SQL Component Generated .dll
  • 15. In-memory data structures 15 Rows • New row format Structure of the row is optimized for memory residency and access • One copy of row Indexes point to rows, they do not duplicate them Indexes • Hash index for point lookups • Memory-optimized nonclustered index for range and ordered scans • Do not exist on disk – recreated during recovery
  • 16. Memory-optimized table: Row format Key Points • Begin/End timestamp determines row’s validity • No data or index page; just rows • Row size limited to 8060 bytes to allow data to be moved to disk-based table • Not every SQL table schema is supported Row header Payload (table columns) Begin Ts End Ts StmtId IdxLinkCount 8 bytes 8 bytes 4 bytes 2 bytes 8 bytes * (IdxLinkCount – 1)
  • 17. Key lookup: B-tree vs. memory-optimized table Matching index record Hash index on Name R1 R2 R3 Non-clustered index
  • 19. • No DML triggers • No FOREIGN KEY or CHECK constraints • No IDENTITY columns • 8060 byte hard limit for row length • No UNIQUE indexes other than for the PRIMARY KEY • A maximum of 8 indexes, including the index supporting the PRIMARY KEY • No schema changes are allowed once a table is created (drop/recreate) • Indexes are always and ONLY created at as part of the table creation In-Memory OLTP Limitations
  • 20. Indexes Comparison for different kinds of operations Operation Memory hash Memory nonclustered Disk Index Scan, retrieve all table rows. Yes Yes Yes Index seek (=). Yes (Full key required.) Yes 1 Yes Index seek (>, <, <=, >=, BETWEEN). No (index scan) Yes 1 Yes Retrieve rows in a sort-order matching the index definition. No Yes Yes Retrieve rows in a sort-order matching the reverse of the index definition. No No Yes
  • 21. Memory management 21 Data resides in memory at all times • Must configure SQL server with sufficient memory to store memory-optimized tables • Failure to allocate memory will fail transactional workload at run-time • Integrated with SQL Server memory manager and reacts to memory pressure where possible Integration with Resource Governor • “Bind” a database to a resource pool • Mem-opt tables in a database cannot exceed the limit of the resource pool • Hard limit (80% of phys. memory) to ensure system remains stable under memory pressure
  • 22. Garbage collection 22 Stale Row Versions • Updates, deletes, and aborted insert operations create row versions that (eventually) are no longer visible to any transaction • Slow down scans of index structures • Create unused memory that needs to be reclaimed (i.e. Garbage Collected) Garbage Collection (GC) • Analogous to version store cleanup task for disk-based tables to support Read Committed Snapshot (RCSI) • System maintains ‘oldest active transaction’ hint GC Design • Non-blocking, Cooperative, Efficient, Responsive, Scalable • A dedicated system thread for GC • Active transactions work cooperatively and pick up parts of GC work
  • 23. Cooperative garbage collection Key Points • Scanners can remove expired rows when found • Offloads work from GC thread • Ensures that frequently visited areas of the index are cleaned regularly • A row needs to be removed from all indexes before memory can be freed • Garbage collection is most efficient if all indexes are frequently accessed 100 200 1 John Smith Kirkland 200 ∞ 1 John Smith Redmond 50 100 1 Jim Spring Kirkland 300 ∞ 1 Ken Stone Boston TX4: Begin = 210 Oldest Active Hint = 175
  • 24. Durability 24 Memory-optimized tables can be durable or non-durable • Default is ‘durable’ • Non-durable tables are useful for transient data Durable tables are persisted in a single memory-optimized file group Storage used for memory-optimized has a different access pattern than for disk tables File group can have multiple containers (volumes) Additional containers aid in parallel recovery; recovery happens at the speed of IO
  • 25. On-disk storage 25 Filestream is the underlying storage mechanism Checksums and single-bit correcting ECC on files Data files • ~128MB in size, write 256KB chunks at a time • Stores only the inserted rows (i.e. table content) • Chronologically organized streams of row versions Delta files • File size is not constant, write 4KB chunks at a time. • Stores IDs of deleted rows
  • 26. Logging for memory-optimized tables 26 Uses SQL transaction log to store content Each log record contains a log record header followed by opaque memory optimized-specific log content All logging for memory-optimized tables is logical • No log records for physical structure modifications. • No index-specific / index-maintenance log records. • No UNDO information is logged Recovery Models All three recovery models are supported
  • 27. Backup for memory-optimized tables 27 Integrated with SQL Database Backup • Memory-Optimized file group is backed up as part SQL Server database backup • Existing backup scripts work with minimal or no changes • Transaction log backup includes memory-optimized log records Not supported Differential backup
  • 28. Recovery for memory-optimized tables 28 Analysis Phase Finds the last completed checkpoint Data Load • Load from set of data/delta files from the last completed checkpoint • Parallel Load by reading data/delta files using 1 thread / file Redo phase to apply tail of the log • Apply the transaction log from last checkpoint • Concurrent with REDO on disk-based tables No UNDO phase for memory-optimized tables Only committed transactions are logged
  • 29. Myth #1 Reality SQL Server In-Memory OLTP is a recent response to competitors’ offerings
  • 30. Myth #2 Reality In-Memory OLTP is like DBCC PINTABLE
  • 31. Myth #3 Reality In-Memory Databases are new separate products
  • 32. Myth #4 Reality You can use In-Memory OLTP in an existing SQL Server app with NO changes whatsoever
  • 33. Myth #5 Reality Since tables are in memory, the data is not Durable or Highly Available – I will lose it after server crash
  • 35. In-memory OLTP summary 35 What’s being delivered • High-performance, memory-optimized OLTP engine integrated into SQL Server and architected for modern hardware trends Main benefits • Optimized for in-memory data up to 20–30 times throughput ‐ Indexes (hash and range) exist only in memory; no buffer pool, B-trees ‐ T-SQL compiled to machine code via C code generator and Visual C compiler ‐ Core engine uses lock-free algorithms; no lock manager, latches, or spinlocks • Multiversion optimistic concurrency control with full ACID support • On-ramp existing applications • Integrated experience with same manageability, administration, and development experience
  • 37. Cardinality 37 • Execution Plans uses Cardinality in order to get an estimation of number of rows for each query • Although the new cardinality still works based on Statistics the algorithm has been dramatically changed • Databases in native compatibility level (120) works with the new estimator version • Change that behavior with the OPTION (QUERYTRACEON 9481) to still be executed with the old version (per Query basis) • Databases in compatibility level 110 could be executed with the new version when using QUERYTRACEON 2312 hint (per Query basis)
  • 38. Scenarios 38 • New cardinality estimates use an average cardinality for recently added ascending data (ascending key problem) without Statistics Update ‐ Old Version estimates 0 rows ‐ New Version uses average cardinality • New cardinality estimates assume filtered predicates on the same table have some correlation ‐ Old and New Version depends on the specific sample • New cardinality estimates assume filtered predicates on different tables are independent ‐ Old and New Version depends on the specific sample
  • 39. 39 • Check the performance of your workloads and do the math ‐ Compatibility Level 110 ‐ Compatibility Level 110 and add OPTION (QUERYTRACEON 2312) to some querys ‐ Native Compatibility Level (120) ‐ Native Compatibility Level (120) and add OPTION (QUERYTRACEON 9481) to some querys Suggestions
  • 41. SQL Server 2014 Security Enhancements
  • 42. Separation of duties enhancement • Four new permissions ‐ CONNECT ANY DATABASE (server scope) ‐ IMPERSONATE ANY LOGIN (server scope) ‐ SELECT ALL USER SECURABLES (server scope) ‐ ALTER ANY DATABASE EVEN SESSION (database scope) • Main benefit ‐ Greater role separation to restrict multiple DBA roles ‐ Ability to create new roles for database administrators who are not sysadmin (super user) ‐ Ability to create new roles for users or apps with specific purposes
  • 43. Best practices for separation of duties • Eliminate the use of superusers (SA login, SYSADMIN server role, DBO database user) • Use permission system rather than superuser • Use CONTROL SERVER (server level) and CONTROL DATABASE (database level) instead and use DENY for specifics • Always document the user of ownership chains
  • 44. Backup encryption • Increase security of backups stored separate from the instance (another environment such as the Cloud) • Encryption keys can be stored on-premises while backup files in the cloud • Support non-encrypted databases (don’t need to turn on Transparent Data Encryption anymore) • Different policies for databases and their backups
  • 45. T-SQL BACKUP / RESTORE BACKUP DATABASE <dbname> TO <device> = <path to device> WITH ENCRYPTION ( ALGORITHM = <Algorithm_name> , { SERVER CERTIFICATE = <Encryptor_Name> | SERVER ASYMMETRIC KEY = <Encryptor_Name> } ); No changes to RESTORE
  • 46. T-SQL views • msdb.dbo.backupset • msdb.dbo.backupmediaset backup_set_id name key_algorithm encryptor_thumbprint encryptor_type 3 Full Backup NULL NULL NULL 4 Full Backup aes_256 0x00B1BD62DAA0196 CERTIFICATE media_set_id is_password_protected is_compressed is_encrypted 3 0 1 0 4 0 1 1
  • 47. Additional details • AES 128, AES 192, AES 256, and Triple DES • Unique backup key is generated for each backup • Certificate • Asymmetric key from an EKM provider only • All operations require certificate or key • Appended backup is not supported • Compression has no effect on pre-encrypted databases
  • 48. SQL Server 2014 AlwaysOn Enhancements
  • 49. AlwaysOn in SQL Server 2014 • What’s being delivered • Increase number of secondaries from four to eight • Increase availability of readable secondaries • Support for Windows Server 2012 CSV • Enhanced diagnostics • Main benefits • Further scale out read workloads across (possibly geo-distributed) replicas • Use readable secondaries despite network failures (important in geo-distributed environments) • Improve SAN storage utilization • Avoid drive letter limitation (max 24 drives) via CSV paths • Increase resiliency of storage failover • Ease troubleshooting
  • 50. Description • Increase number of secondaries (4–8) • Max number of sync secondaries is still two Increase number of Availability Group secondaries Reason • Customers want to use readable secondaries • One technology to configure and manage • Many times faster than replication • Customers are asking for more database replicas (4–8) • To reduce query latency (large-scale environments) • To scale out read workloads
  • 51. Description Allow FCI customers to configure CSV paths for system and user databases Support for Windows Server Cluster Shared Volumes Reason • Avoid drive letter limitation on SAN (max 24 drives) • Improves SAN storage utilization and management • Increased resiliency of storage failover (abstraction of temporary disk-level failures) • Migration of SQL Server customers using PolyServe (to be discontinued in 2013)
  • 52. Description Allow FCI customers to configure CSV paths for system and user databases Support for Windows Server Cluster Shared Volumes Reason • Avoid drive letter limitation on SAN (max 24 drives) • Improves SAN storage utilization and management • Increased resiliency of storage failover (abstraction of temporary disk-level failures) • Migration of SQL Server customers using PolyServe (to be discontinued in 2013)
  • 53. SQL Server 2014 Resource Governor with IO
  • 54. Resource Governor goals • Ability to differentiate workloads • Ability to monitor resource usage per group • Limit controls to enable throttled execution or prevent/minimize probability of “run-aways” • Prioritize workloads • Provide predictable execution of workloads • Specify resource boundaries between workloads
  • 56. Complete resource governance • What’s being delivered ‐ Add max/min IOPS per volume to Resource Governor pools ‐ Add DMVs and perfcounters for IO statistics per pool per volume ‐ Update SSMS Intellisense for new T-SQL ‐ Update SMO and DOM for new T-SQL and objects • Main benefits ‐ Better isolation (CPU, memory, and IO) for multitenant workloads ‐ Guarantee performance in private cloud and hosters scenario
  • 57. Resource pools • Represents physical resources of server • Can have one or more workloads assigned to pool • Pool divided into shared and non-shared • Pools control min/max for CPU/memory and now IOPS CREATE RESOURCE POOL pool_name [ WITH ( [ MIN_CPU_PERCENT = value ] [ [ , ] MAX_CPU_PERCENT = value ] [ [ , ] CAP_CPU_PERCENT = value ] [ [ , ] AFFINITY {SCHEDULER = AUTO | (Scheduler_range_spec) | NUMANODE = (NUMA_node_range_spec)} ] [ [ , ] MIN_MEMORY_PERCENT = value ] [ [ , ] MAX_MEMORY_PERCENT = value ] [ [ , ] MIN_IOPS_PER_VOLUME = value ] [ [ , ] MAX_IOPS_PER_VOLUME = value ]) ]
  • 58. Resource pools • Minimums across all resource pools can not exceed 100 percent • Non-shared portion provides minimums • Shared portion provides maximums • Pools can define min/max for CPU/Memory/IOPS ‐ Mins defined non-shared ‐ Max defined shared
  • 59. Steps to implement Resource Governor • Create workload groups • Create function to classify requests into workload group • Register the classification function in the previous step with the Resource Governor • Enable Resource Governor • Monitor resource consumption for each workload group • Use monitor to establish pools • Assign workload group to pool
  • 60. Resource Governor scenarios • Scenario 1: I just got a new version of SQL Server and would like to make use of resource governor. How can I use it in my environment? • Scenario 2 (based on Scenario 1): Based on monitoring results I would like to see an event any time a query in the ad-hoc group (groupAdhoc) runs longer than 30 seconds. • Scenario 3 (based on Scenario 2): I want to further restrict the ad-hoc group so it does not exceed 50 percent of CPU usage when all requests are cumulated.
  • 61. Monitoring Resource Governor • System views ‐ sys.resource_governor_resource_pools ‐ sys.resource_governor_configuration • DMVs ‐ sys.dm_resource_governor_resource_pools ‐ sys.dm_resource_governor_resource_pool_volumes ‐ sys.dm_resource_governor_configuration • New performance counters ‐ SQL Server:Resource Pool Stats ‐ SQL Server:Workload group • XEvents ‐ file_read_enqueued ‐ file_write_enqueued
  • 63. Backup to Windows Azure What’s being delivered • SQL Server supports backups to and restores from the Windows Azure Blob storage service (UI, T-SQL, PowerShell commandlets) Main benefit: Take advantage of Windows Azure Blob storage • Flexible, reliable (3-copies geo-DR), and limitless off-site storage • No need of backup media management • No overhead of hardware management CREATE CREDENTIAL mystoragecred WITH IDENTITY = ‘mystorage', SECRET = ‘<your storage access key> BACKUP DATABASE mydb TO URL ='https://mystorage.blob.core.windows.net/backup-container/mydb- 20130411.bak' WITH CREDENTIAL = ‘mystoragecred', FORMAT, COMPRESSION, STATS = 5, MEDIANAME = ‘mydb backup 20130411', MEDIADESCRIPTION = 'Backup of mydb'
  • 64. Backup to Windows Azure Windows Azure storage WA WindowsAzure Blobs • On-site/off-site storage costs • Device management costs Box • XDrives limited to 1 terabyte • Max 16 drives • Manage drives and policy • Near “bottomless” storage • Off-site, geo-redundant • No provisioning • No device management • Media safety (decay-free) • Remote accessibility
  • 65. Backup to Windows Azure • Simple configuration UI • Easy creation of Azure credential • No overhead
  • 66. Backup to Windows Azure Tool • What is it? ‐ Stand-alone Tool that adds backup to Windows Azure capabilities and backup encryption to prior versions of SQL Server • Benefits ‐ One Cloud Backup strategy across prior versions of SQL Server including 2005, 2008, and 2008 R2 ‐ Adds backup encryption to prior versions, locally or in the cloud ‐ Takes advantage of backup to Azure ‐ Easy configuration
  • 67. Managed backup to Azure • What’s being delivered ‐ Agent that manages and automates SQL Server backup policy • Main benefit ‐ Large-scale management and no need to manage backup policy  Context-aware – for example, workload/throttling  Minimal knobs – control retention period  Manage whole instance or particular databases ‐ Take advantage of backup to Azure  Inherently off-site  Geo-redundant  Minimal storage costs  Zero hardware management Example: EXEC smart_admin.sp_set_db_backup @database_name='TestDB', @storage_url=<storage url>, @retention_days=30, @credential_name='MyCredential', @enable_backup=1
  • 68. SQL Server 2014 Database Data and Log Files in Azure Storage
  • 69. SQL Server data and log files in Windows Azure storage • What’s being delivered ‐ Ability to move data and log files in Windows Azure Storage, while keeping the compute node of SQL Server on-premises ‐ Transparent Data Encryption (TDE) is supported • Main benefits ‐ No application changes required ‐ Centralized copy of data and log files ‐ Enjoy unlimited storage capacity in Azure Storage (built in HA, SLA, geo-DR) ‐ Secure because TDE encryption key can be stored on-premises ‐ Restore database is simply an attach operation
  • 70. SQL Server data and log files in Windows Azure storage
  • 71. SQL Server 2014 Deploy Database to Windows Azure Wizard
  • 73. Deploy databases to Windows Azure VM • What’s being delivered ‐ New wizard to deploy databases to SQL Server in Windows Azure VM ‐ Can also create a new Windows Azure VM if needed • Main benefits ‐ Easy to use  Perfect for database administrators new to Azure and for ad hoc scenarios ‐ Complexity hidden  Detailed Azure knowledge not needed  Almost no overhead: defining factor for time-to-transfer is database size
  • 74. Call to action • Download Trial SQL Server 2014 http://technet.microsoft.com/en-US/evalcenter/dn205290.aspx • Trial Azure http://azure.microsoft.com/en-us/pricing/free-trial/ • SQL Server http://www.microsoft.com/SQLServer

Editor's Notes

  • #41: select * from [sql] select * from [sql] where c1>100000 Insert 5000 rows into [sql] Try Estimated plan Ctrl-L for all those querys at the same time select * from [sql] where c1>100000 option (querytraceon 2312) select * from [sql] where c1>100000 option (querytraceon 9481) select * from [sql] where c1>100000
  • #65: You can use the Transact-SQL ALTER TABLE...SWITCH statement to quickly and efficiently transfer subsets of your data in the following ways: Assigning a table as a partition to an already existing partitioned table. Switching a partition from one partitioned table to another. Reassigning a partition to form a single table.
  • #73: Not only are we enabling new unique hybrid scenarios, we are also simplify cloud adoption for our customers. With SQL Server 2014 we will also ship a new migration wizard that will help DBAs easily migrate their on-premises SQL Server instance to Windows Azure and again directly through SSMS as you can see in the screen shot there, point and click and you instance will be up and running in Azure in no time. Once you become familiar with Windows Azure you can start to take advantage of the Windows Azure Virtual Machine to run many scenarios in the cloud including fast dev/test of your SQL Server applications, moving existing applications, doing hybrid scenarios like we talked about, BI scenarios in the cloud because you have full SQL Server functionality including all of the BI services. In addition you have full control over the VM so if you want to put your corporate anti-virus on the VM you can. Once you have become comfortable with the Windows Azure environment you can take advantage of Windows Azure SQL Database service offering that will speed development of your new database application even faster because you don’t have to manage the database, it is a service, you don’t have to patch the OS or database we take care of that, all you do is develop your application using the service. The SQL Database service also has unique cloud features like dynamic scalability of the database using Federations like Flavorus did to achieve their business goals. In addition this database service also offers an SLA for the database running inside the VM and you don’t have think about setting up high availability because it is built-in to the database service by default. This is where we see cloud applications doing fast development, less maintenance and faster time to market.