HomeSQL Server 2014SQL Server 2014 In-Memory OLTP (Hekaton) Limitations

Comments

SQL Server 2014 In-Memory OLTP (Hekaton) Limitations — 3 Comments

  1. “For memory-optimized tables, some of the features not supported are: IDENTIFY or SEQUENCE columns…” I think this is misleading. Sequences are not tied to tables; rather, sequences are bound to a schema. The above comment from Ulises is mostly correct but it also glosses over the fact that sequences are not tied to tables. As far as I can tell, there’s really no such thing as sequence “columns” in Microsoft SQL Server.

    Also, this article seems to be incorrect when it says that “Merge statement” is not supported. Where did that come from? http://blogs.technet.com/b/dataplatforminsider/archive/2014/01/22/merge-operation-in-memory-optimized-tables.aspx talks about how the MERGE statement is handled in memory-optimized tables.

  2. Wait, I think I conflated the SQL Merge statement with the “merge phase” of memory management for these tables. The last paragraph of my previous comment can be ignored or removed. Thanks.

Leave a Reply to DWalker Cancel reply

Your email address will not be published. Required fields are marked *

HTML tags allowed in your comment: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>