title: Does Sql Server 2014's "Hekaton" compiled stored procedures address parameter sniffing issues?
body: <p>SQL Server 2014's <a href="http://research.microsoft.com/pubs/193594/Hekaton%20-%20Sigmod2013%20final.pdf" rel="nofollow noreferrer">"Hekaton" in-memory table optimization</a> proclaims, "Native compilation of business logic in stored procedures." Because of issues with "parameter sniffing" (see <a href="https://stackoverflow.com/questions/12979493/multi-tenant-sql-server-databases-and-parameter-sniffing">here</a> and <a href="http://www.sommarskog.se/query-plan-mysteries.html" rel="nofollow noreferrer">here</a>) in SQL Server 2012 and earlier, however, I have always been forced to design most of my stored procedures with <a href="http://www.benjaminnevarez.com/2010/06/how-optimize-for-unknown-works/" rel="nofollow noreferrer"><code>OPTIMIZE FOR UNKNOWN</code></a> (or its equivalent). This effectively prevents query plans from being cached and forces SQL Server to recompile/re-optimize queries each time they are run. With a significant portion of Hekaton's performance gains coming from reuse of native compiled queries, does SQL Server 2014 do anything to address the parameter sniffing issue so I can actually use compiled queries?</p>