An introduction to SQL 2014 in-memory OLTP know as Hekaton (XTP) Introduction. I presented this session at SQL User Group Melbourne sometime back. Suitable for people who are getting to know more about Hekaton

1. Hekaton (XTP)
Tara Shankar Jana
PFE- Microsoft Australia

2. Why Hekaton (XTP)?
Market need for ever higher throughput and
lower latency OLTP at a lower cost
HW trends demand architectural changes on
RDBMS to meet those demands
Stalled CPU’s, Attainment of Balanced Systems.
Hekaton is: High performance, memoryoptimized OLTP engine integrated into SQL Server
and architected for modern hardware trends
2

3. Why Hekaton (XTP)?
Market need for ever higher throughput and
lower latency OLTP at a lower cost
HW trends demand architectural changes on
RDBMS to meet those demands
Stalled CPU’s, Attainment of Balanced Systems.
Hekaton is: High performance, memoryoptimized OLTP engine integrated into SQL Server
and architected for modern hardware trends
3

4. What is Hekaton (XTP)?
Hekaton is Greek for “hundreds,” and it was given this name for its
ability to speed up database function 100x (possibly)
With a new latch-free technology Hekaton is claimed to
dramatically increase performance.
SQL Server 2014 allows you to migrate the most-used tables in an
existing database to memory-optimised 'Hekaton' technology.
It is also known as SQL Server In-Memory database, touted to
accelerate transaction throughput up to 30x performance increases
on existing hardware.
4

5. What is Hekaton (XTP)?
Hekaton is Greek for “hundreds,” and it was given this name for its
ability to speed up database function 100x (possibly)
With a new latch-free technology Hekaton is claimed to
dramatically increase performance.
Hekaton doesn’t use SQL’s Buffer Cache
SQLor VAS, it allows youeverything most-used tables in an
Server 2014 stores to migrate the in the RAM
existing database to memory-optimised 'Hekaton' technology.
It is also known as SQL Server In-Memory database, touted to
accelerate transaction throughput up to 30x performance increases
on existing hardware.
5

6. Drivers
Architectural Pillars
Customer
Benefits
In-Memory OLTP – Architectural Pillars
High performance
data operations
Efficient businesslogic processing
Frictionless scaleup
Hybrid engine and
integrated
experience
Main-Memory
Optimized
T-SQL Compiled to
Machine Code
High Concurrency
SQL Server
Integration
• Optimized for in-memory
data
• Indexes (hash and
range) exist only in
memory
• No buffer pool, B-trees
• Stream-based storage
• T-SQL compiled to
machine code via C code
generator and VC
• Invoking a procedure is
just a DLL entry-point
• Aggressive
optimizations @
compile-time
• Multi-version optimistic
concurrency control with
full ACID support
• Core engine uses lockfree algorithms
• No lock manager, latches
or spinlocks
Business
Hardware trends
Steadily declining
memory price, NVRAM
Stalling CPU clock rate
• Same
manageability, administr
ation & development
experience
• Integrated queries &
transactions
• Integrated HA and
backup/restore
Many-core processors
TCO

7. In-Memory OLTP Integration and Application
Migration
Client App
TDS Handler and Session Management
Natively Compiled
SPs and Schema
Parser, Cat
alog, Opti
mizer
Native
Compiler
Key
Existing
SQL
Component
T-SQL Query Execution
In-mem
OLTP
Component
Query
Interop
T1
T2
T3
Tables
Indexes
T1
Memory Optimized Data
Filegroup
Buffer Pool for Tables & Indexes
SQL Server.exe
Memory Optimized Tables & Indexes
T2
Transaction Log
T3
T1
T2
Data Filegroup
T3
Generated
.dll

8. HEKATON- XTP (How to
Create Memory-Optimized
Tables)
demo

9. HEKATON- AMR TOOL
demo

10. For more consulting and support offerings from
Microsoft, contact your Microsoft Services representative or
visit www.microsoft.com.au/services.
Contact
Email: tarasden@hotmail.com
tarasha@Microsoft.com
Blog: http://blogs.msdn.com/b/sql-bi-sapcloud-crm_all_in_one_place/
Website: http://sqlmasters.jimdo.com
© 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The
information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market
conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT
MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION