Post reply

Building Natively compiled stored procedures in SQL 2014

  • April 9, 2014 at 10:52 am

    #290117

    Why, how, what purposes and restrictions.

  • May 6, 2014 at 9:28 am

    #1711133

    bump

  • May 29, 2014 at 11:26 am

    #1717466

    Steve Jones - SSC Editor (5/6/2014)

    bump

    I'd be happy to take this on. I began hinting at memory-optimized tables and stored procs in my article on SQL Server 2014 DMVs, so this would be a good extension from that.

  • May 29, 2014 at 4:44 pm

    #1717634

    Feel free. Probably won't publish until our overview of MO tables goes out in late June, but feel free to submit anytime.

  • May 30, 2014 at 12:27 pm

    #1717916

    Sending it over now --- I've really enjoyed messing with the memory optimized features in SQL Server 2014.

    Many of the initial responses by the community were very lackluster, citing the restrictions as reasons to not waste your time with it, but the performance gains can be unbelievably good.

    Poorly written SQL in a natively compiled stored proc can easily blow away the performance of traditional procs/tables, no matter how well written. Not at all advocating bad SQL, but it's a different world than what we're used to and many of the restrictions are there for a good reason and aren't just indicative of lousy design.

Viewing 5 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply