Export (0) Print
Expand All
This topic has not yet been rated - Rate this topic

Running Stored Procedures (OLE DB)

When executing statements, calling a stored procedure on the data source (instead of executing or preparing a statement in the client application directly) can provide:

  • Higher performance.

  • Reduced network overhead.

  • Better consistency.

  • Better accuracy.

  • Added functionality.

The SQL Server Native Client OLE DB provider supports three of the mechanisms that SQL Server stored procedures use to return data:

  • Every SELECT statement in the procedure generates a result set.

  • The procedure can return data through output parameters.

  • The procedure can have an integer return code.

The application must be able to handle all of these outputs from stored procedures.

Different OLE DB providers return output parameters and return values at different times during result processing. In case of the SQL Server Native Client OLE DB provider, the output parameters and return codes are not supplied until after the consumer has retrieved or canceled the result sets returned by the stored procedure. The return codes and the output parameters are returned in the last TDS packet from the server.

Providers use the DBPROP_OUTPUTPARAMETERAVAILABILITY property to report when it returns output parameters and return values. This property is in the DBPROPSET_DATASOURCEINFO property set.

The SQL Server Native Client OLE DB provider sets the DBPROP_OUTPUTPARAMETERAVAILABILITY property to DBPROPVAL_OA_ATROWRELEASE to indicate that return codes and output parameters are not returned until the result set is processed or released.

Did you find this helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2014 Microsoft. All rights reserved.