>>
>>Hi Kevin,
>>
>>Our app is a high-insert app. Is the performance gain from Hekaton as significant if the current DB (2008R2) fits in memory and is backed by SSD?
>
>Possibly, but can't say with 100% certainty.
>
>There is a tool you can download - AMR, from Microsoft. It will analyze and monitor/profile your database to see if it's a candidate for Hekaton.
>
>http://sqlmag.com/sql-server-2014/sql-server-2014-analysis-migrate-report-tool-amr
>
>One thing - I believe Hekaton is only available in the Enterprise version of 2014.
>
>Also - there are several T-SQL functions that can't be used when inserting rows into Hekaton tables (a big one is date functions). So you'd have to abstract out your stored proc inserts to receiving nothing but scalar variables that are pre-populated with the values you want.

Bummer... Just like materialized and indexed views are only available in the enterprise version. That is just not an option for us. I see you're still a fan of stored procs. What is the relation between Hekaton and stored procs?