Top 5 T-SQL Improvementsin SQL Server 2014

That’s not a Hekaton Talk!

@BorisHristov

So who am I?

things that can make every dev’s life better

Here’s how this will go…

time

Delayed Durability

Atomic

Isolated

Consistent

Durable

Every transaction has to be…

Data pages are located in, or read into, the buffer cache and then modified

2

Modification is recorded in transaction log on disk3

Later, checkpoint writes dirty pages to database

4

Buffer Cache

Transaction’s lifecycle

Here’s the reason why it’s slow

Data pages are located in, or read into, the buffer cache modified and results returned

2

Modification is recorded in transaction log on disk3

Later, checkpoint writes dirty pages to database

4

Buffer Cache

Transaction’s lifecycle

Yes, you can lose data!

DEMODelayed Durability

SELECT INTO

Prior SQL Server 2014:Serial Execution Plans

SQL Server 2014:Parallel Execution Plans

Why don’t we speed up a bit?

Talk with the DBAs to design a proper disk and data layout!

You want that speed, right?

DEMOSELECT INTO

Cardinality Estimator

Why is the CE so important?

Why is the CE so important?

The CE has not been changed since SQL Server 7.0

…and at the same time

Queries with MultiplePredicates

Queries Joining Multiple Tables

New Data Not Presentedin the Stats

Almost everywhere…

(this, oh btw, means you have to test a lot!)

Where to expect changes?

DEMOCardinality Estimator

Inline Index Definitions

SQL Server 2012

SQL Server 2014

Remember this improvement

Partitioning Improvements

Numbers

0

…

8000

Partition 2

2501

…

4000

Partition 3

4001

…

8000

Why is partitioning both cool and not?

Partition 1

0

…

2500

DEMOPartitioning Improvements

In summary

Delayed Durability

Parallel SELECT INTO

Cardinality Estimator

Inline Index Creation

Partitioning Improvements

Testing is important!

Resources you can use

Just a click away!

Thank you!

Contacts:brshristov@live.com@BorisHristovwww.borishristov.com