>>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?
>
>
>Yes, the new in-memory OLTP engine is only for the Enterprise edition, and only for the 64-bit version. I know many who use the BI edition of SQL Server are understandably frustrated, but I can at least see the requirement for 64-bit.
>
>Yes, still a fan of stored procs. I think every client I've had since 2004 has used them extensively.

I'd say there's nothing inherently wrong with stored procs, unless the "reasons" for using them are: 1 - they are "precompiled" and 2 they prevent sql injection and 3 they are the best API for CRUD. None of these things are true.

That reminds me of a question I have been wanting to pose. Assuming I have 1000 cached execution plans and I compare 1000 sprocs that each run a query vs directly running the individual queries,

Wouldn't SQL have to lookup the sproc, then look at the query, then determine which plan, then execute
instead of
look at the query, then determine which plan, then execute?

in other words, wouldn't having to scan the 1000 sprocs take extra time? I'm pretty sure that time would be less than the time spent transmitting the raw SQL vs transmitting the sproc name, but it seems reasonable.