Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 

James Serra's Blog

James is currently a Senior Business Intelligence Architect/Developer and has over 20 years of IT experience. James started his career as a software developer, then became a DBA 12 years ago, and for the last five years he has been working extensively with Business Intelligence using the SQL Server BI stack (SSAS, SSRS, and SSIS). James has been at times a permanent employee, consultant, contractor, and owner of his own business. All these experiences along with continuous learning has helped James to develop many successful data warehouse and BI projects. James has earned the MCITP Business Developer 2008, MCITP Database Administrator 2008, and MCITP Database Developer 2008, and has a Bachelor of Science degree in Computer Engineering. His blog is at .

SQL Server 2014: In-memory OLTP Engine, code-name: Hekaton

What looks to be the biggest and best new feature in SQL Server 2014 is called the “In-memory OLTP Engine”, code-name: Hekaton.  In short, Hekaton is a SQL Server In-memory OLTP Engine.  Hekaton provides in-memory OLTP capabilities built into core SQL Server database to significantly improve the performance of your database application.  Hekaton is installed with the SQL Server 2014 Engine without requiring any additional actions and allows in-memory performance benefits without rewriting your database application.  You can also increase performance of existing SQL Server applications without having to refresh your hardware.  Hekaton is easy to deploy and allows you to access the other rich features in SQL Server, while taking advantage of in-memory performance.

This complements the existing in-memory data-warehousing and business-intelligence (BI) capabilities already in SQL Server via xVelocity.  Hekaton could benefit DW/BI solutions in two ways that I see: 1) By speeding up the time it takes to pull data from a source system that is in-memory into the data warehouse, and 2) Instead of persisting staging data in tables on disk, you can store them in memory.

Here is the description from the Microsoft site:

Hekaton in-memory OLTP: In-memory database technology that will provide breakthrough performance gains 10 times for existing apps and up to 50 times for new applications optimized for in-memory performance with no additional hardware required.  There will be a diagnostic tool that will suggest which databases and tables are the best candidates to run in-memory.  The “Hekaton” codename will fade and  it will be referred to as the SQL Server In-Memory OLTP Engine.

More info:

In-Memory OLTP White Paper

Edgenet Gain Real-Time Access to Retail Product Data with In-Memory Technology

First steps with Extreme Transaction Processing – Hekaton

SQL Server 2014 In-Memory Technologies: Blog Series Introduction

Getting Started with SQL Server 2014 In-Memory OLTP

SQL Server 2014 CTP1 native compiled Hekaton procedures are faster than regular procedures

Supported and unsupported datatypes with Hekaton tables

Hekaton data and code – where does that stuff actually live?

Geek City: SQL Server 2014 In-Memory OLTP (“Hekaton”) Whitepaper

First baby steps with SQL Server 2014 CTP1

Exploring In-memory OLTP Engine (Hekaton) in SQL Server 2014 CTP1

SQL 2014 In-Memory OLTP ‘Hekaton’: training videos and white papers

Hekaton: Transforming Query Plans into C Code

In-Memory (Memory Optimized) Tables in SQL Server 2014

In-Memory OLTP Q & A: Myths and Realities

Architectural Overview of SQL Server 2014’s In-Memory OLTP Technology

SQL Server 2014 hastens transaction processing

A Tour of the Hekaton AMR Tool

Hardware Considerations for In-Memory OLTP in SQL Server 2014

SQL Server 2014 In-Memory OLTP: App Migration Scenario Leveraging the Integrated Approach

Extreme Transaction Processing (XTP, Hekaton) – the solution to everything?

How Memory-Optimized Database Technology is Integrated into SQL Server 2014

Comments

Leave a comment on the original post [www.jamesserra.com, opens in a new window]

Loading comments...