Natively Compiled Stored Procedures

Natively compiled stored procedures are Transact-SQL stored procedures compiled to native code that access memory-optimized tables. Natively compiled stored procedures allow for efficient execution of queries and business logic in the stored procedure. For more details about the native compilation process, see Native Compilation of Tables and Stored Procedures. For more information about migrating disk-based stored procedures to natively compiled stored procedures, see Migration Issues for Natively Compiled Stored Procedures.

Note

One difference between interpreted (disk-based) stored procedures and natively compiled stored procedures is that an interpreted stored procedure is compiled at first execution whereas a natively compiled stored procedure is compiled when it is created. With natively compiled stored procedures, many error conditions (arithmetic overflow, type conversion, and some divide-by-zero conditions) can be detected at create time and will cause creation of the natively compiled stored procedure to fail. With interpreted stored procedures, these error conditions will typically not cause a failure when the stored procedure is created, but all executions will fail.

Topics in this section:

• Creating Natively Compiled Stored Procedures

• Atomic Blocks

• Supported Constructs in Natively Compiled Stored Procedures

• Using Try..Catch in Natively Compiled Stored Procedures

• Supported Constructs on Natively Compiled Stored Procedures

• Natively Compiled Stored Procedures and Execution Set Options

• Best Practices for Calling Natively Compiled Stored Procedures

• Monitoring Performance of Natively Compiled Stored Procedures

• Calling Natively Compiled Stored Procedures from Data Access Applications

See Also

Memory-Optimized Tables