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 (Hekaton) Limitations

One of the biggest new features in SQL Server 2014 is SQL Server In-Memory OLTP, known mostly by its code name of Hekaton (see SQL Server 2014: In-memory OLTP Engine, code-name: Hekaton).  Basically, this puts tables in memory, giving a potentially huge performance boost when accessing these tables, especially with writes (to perform your own performance testing, check out SQL Server 2014 CTP2 In-Memory OLTP Sample).  But be aware that there are currently many features that In-Memory OLTP does not support:

For memory-optimized tables, some of the features not supported are: IDENTIFY or SEQUENCE columns, foreign key constraints, check constraints, MERGE statement, DML triggers, XML/CLR/LOB data types, compression.

Also, with In-Memory OLTP you can natively compile stored procedures (with native_compilation), but the stored procedures can only access in-memory tables.  And there are many features that you cannot use inside a natively compile stored procedure, such as: cursors, CASE statement, CTEs, user-defined functions, UNION statement, PIVOT statement, DISTINCT statement, and many more.

See Transact-SQL Constructs Not Supported by In-Memory OLTP for a comprehensive list of what is not supported.

More info:

SQL SERVER 2014 IN-MEMORY OLTP HEKATON USEFUL LINKS

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

SQL Server 2014 In-Memory OLTP Architecture and Data Storage

Natively Compiled Stored Procedures with SQL Server 2014

Comments

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

Loading comments...