When you use memory-optimized table variables outside the natively compiled stored procedures, a LCK_M_SCH_M (schema modify lock) is taken on the corresponding memory-optimized table type during destructing the table variable. In this situation, the concurrent declaration of memory-optimized table variables outside natively compiled stored procedures is blocked.
The issue was first fixed in the following cumulative update of SQL Server.
Each new cumulative update for SQL Server contains all the hotfixes and all the security fixes that were included with the previous cumulative update. Check out the latest cumulative updates for SQL Server:
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Article ID: 2984629 - Last Review: 18 Aug 2014 - Revision: 1
Microsoft SQL Server 2014 Developer, Microsoft SQL Server 2014 Developer, Microsoft SQL Server 2014 Enterprise, Microsoft SQL Server 2014 Enterprise, Microsoft SQL Server 2014 Standard, Microsoft SQL Server 2014 Standard