Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Overview
Stored procedures offer many advantages in data-driven applications. By using stored procedures, you can encapsulate database operations in a single command, optimized for best performance, and enhanced with additional security. Although you can call a stored procedure by passing the stored procedure name followed by parameter arguments as an SQL statement, using the Microsoft.HostIntegration.MsDb2Client.MsDb2Command.Parameters%2A collection of Microsoft.HostIntegration.MsDb2Client.MsDb2Command object enables you to more explicitly define stored procedure parameters, and also to access output parameters and return values.
To call a stored procedure, set the Microsoft.HostIntegration.MsDb2Client.MsDb2Command.CommandType%2A of the Microsoft.HostIntegration.MsDb2Client.MsDb2Command object to StoredProcedure. After the CommandType is set to StoredProcedure, you can use the Parameters collection to define parameters.
You can create an Microsoft.HostIntegration.MsDb2Client.MsDb2Parameter object by using the Microsoft.HostIntegration.MsDb2Client.MsDb2Parameter constructor, or by calling the Add method of the Parameters collection of an Microsoft.HostIntegration.MsDb2Client.MsDb2Command. MsDb2Parameters.Add takes as input either constructor arguments or an existing Microsoft.HostIntegration.MsDb2Client.MsDb2Parameter object. When setting the Value of an Microsoft.HostIntegration.MsDb2Client.MsDb2Parameter to a null reference, use DBNull.Value.
For parameters other than Input parameters, you must set the ParameterDirection property to specify whether the parameter type is InputOutput, Output, or ReturnValue.