SQL Stored Procedures

A stored procedure is a group of Transact-SQL statements compiled into a single execution plan.

Microsoft® SQL Server™ stored procedures return data in four ways:

Output parameters, which can return either data (such as an integer or character value) or a cursor variable (cursors are result sets that can be retrieved one row at a time).
Return codes, which are always an integer value.
A result set for each SELECT statement contained in the stored procedure or any other stored procedures called by the stored procedure.
A global cursor that can be referenced outside the stored procedure.

Stored procedures assist in achieving a consistent implementation of logic across applications. The SQL statements and logic needed to perform a commonly performed task can be designed, coded, and tested once in a stored procedure. Each application needing to perform that task can then simply execute the stored procedure. Coding business logic into a single stored procedure also offers a single point of control for ensuring that business rules are correctly enforced.

Stored procedures can also improve performance. Many tasks are implemented as a series of SQL statements. Conditional logic applied to the results of the first SQL statements determines which subsequent SQL statements are executed. If these SQL statements and conditional logic are written into a stored procedure, they become part of a single execution plan on the server. The results do not have to be returned to the client to have the conditional logic applied; all of the work is done on the server. The IF statement in this example shows embedding conditional logic in a procedure to keep from sending a result set to the application:

IF (@QuantityOrdered < (SELECT QuantityOnHand

FROM Inventory

WHERE PartID = @PartOrdered) )

BEGIN

-- SQL statements to update tables and process order.

END

ELSE

BEGIN

-- SELECT statement to retrieve the IDs of alternate items

-- to suggest as replacements to the customer.

END

Applications do not need to transmit all of the SQL statements in the procedure: they only have to transmit an EXECUTE or CALL statement containing the name of the procedure and the values of the parameters.

Stored procedures can also shield users from needing to know the details of the tables in the database. If a set of stored procedures supports all of the business functions users need to perform, users never need to access the tables directly; they can just execute the stored procedures that model the business processes with which they are familiar.

An illustration of this use of stored procedures is the SQL Server system stored procedures used to insulate users from the system tables. SQL Server includes a set of system stored procedures whose names usually start with sp_. These system stored procedures support all of the administrative tasks required to run a SQL Server system. You can administer a SQL Server system using the Transact-SQL administration-related statements (such as CREATE TABLE) or the system stored procedures, and never need to directly update the system tables.

In earlier versions of SQL Server, stored procedures were a way to partially precompile an execution plan. At the time the stored procedure was created, a partially compiled execution plan was stored in a system table. Executing a stored procedure was more efficient than executing an SQL statement because SQL Server did not have to compile an execution plan completely, it only had to finish optimizing the stored plan for the procedure. Also, the fully compiled execution plan for the stored procedure was retained in the SQL Server procedure cache, meaning that subsequent executions of the stored procedure could use the precompiled execution plan.

SQL Server version 7.0 introduces a number of changes to statement processing that extend many of the performance benefits of stored procedures to all SQL statements. SQL Server 7.0 does not save a partially compiled plan for stored procedures when they are created. A stored procedure is compiled at execution time like any other Transact-SQL statement. SQL Server 7.0 retains execution plans for all SQL statements in the procedure cache, not just stored procedure execution plans. It uses an efficient algorithm for comparing new Transact-SQL statements with the Transact-SQL statements of existing execution plans. If SQL Server 7.0 determines that a new Transact-SQL statement matches the Transact-SQL statement of an existing execution plan, it reuses the plan. This reduces the relative performance benefit of precompiling stored procedures by extending execution plan reuse to all SQL statements.

SQL Server 7.0 offers new alternatives for processing SQL statements. For more information, see Query Processor Architecture.

SQL Server also supports temporary stored procedures that, like temporary tables, are dropped automatically when you disconnect. Temporary stored procedures are stored in tempdb and are useful when connected to earlier versions of SQL Server. Temporary stored procedures can be used in the case where an application builds dynamic Transact-SQL statements that are executed several times. Rather than have the Transact-SQL statements recompiled each time, you can create a temporary stored procedure that is compiled on the first execution, then execute the precompiled plan multiple times. Heavy use of temporary stored procedures, however, can lead to contention on the system tables in tempdb.

However, two features of SQL Server 7.0 eliminate the need for using temporary stored procedures:

SQL Server 7.0 can reuse execution plans from prior SQL statements. This is especially powerful when coupled with the use of the new system stored procedure sp_executesql.
SQL Server 7.0 natively supports the prepare/execute model of OLE DB and ODBC without using any stored procedures.

For more information about alternatives to using temporary stored procedures, see Execution Plan Caching and Reuse.

This simple stored procedure example illustrates three ways stored procedures can return data:

It first issues a SELECT statement that returns a result set summarizing the order activity for the stores in the sales table.
It then issues a SELECT statement that fills an output parameter.
Finally, it has a RETURN statement with a SELECT statement that returns an integer. Return codes are generally used to pass back error checking information. This procedure runs without errors, so it returns another value to illustrate how returned codes are filled.

USE Northwind

GO

DROP PROCEDURE OrderSummary

GO

CREATE PROCEDURE OrderSummary @MaxQuantity INT OUTPUT AS

-- SELECT to return a result set summarizing

-- employee sales.

SELECT Ord.EmployeeID, SummSales = SUM(OrDet.UnitPrice * OrDet.Quantity)

FROM Orders AS Ord

JOIN [Order Details] AS OrDet ON (Ord.OrderID = OrDet.OrderID)

GROUP BY Ord.EmployeeID

ORDER BY Ord.EmployeeID

-- SELECT to fill the output parameter with the

-- maximum quantity from Order Details.

SELECT @MaxQuantity = MAX(Quantity) FROM [Order Details]

-- Return the number of all items ordered.

RETURN (SELECT SUM(Quantity) FROM [Order Details])

GO

-- Test the stored procedure.

-- DECLARE variables to hold the return code

-- and output parameter.

DECLARE @OrderSum INT

DECLARE @LargestOrder INT

-- Execute the procedure, which returns

-- the result set from the first SELECT.

EXEC @OrderSum = OrderSummary @MaxQuantity = @LargestOrder OUTPUT

-- Use the return code and output parameter.

PRINT 'The size of the largest single order was: ' +

CONVERT(CHAR(6), @LargestOrder)

PRINT 'The sum of the quantities ordered was: ' +

CONVERT(CHAR(6), @OrderSum)

GO

The output from running this sample is:

EmployeeID SummSales

----------- --------------------------

1 202,143.71

2 177,749.26

3 213,051.30

4 250,187.45

5 75,567.75

6 78,198.10

7 141,295.99

8 133,301.03

9 82,964.00

The size of the largest single order was: 130

The sum of the quantities ordered was: 51317

SQL Stored Procedures

See Also