Home > Articles > Programming > ASP .NET

  • Print
  • + Share This
This chapter is from the book

Managed Commands with Stored Procedures

Although the example in Listing 3.5 allows you to evaluate data and output only what is desired, a more economical way to get a restricted result set is to use a SQL statement with a WHERE clause. Rather than querying the data store and bringing back all of the records in the table, you can write a SQL statement or stored procedure to bring back only the data you want. Stored procedures typically give better performance to your application than a SQL statement passed via a command.

You can use the Managed Command to call a stored procedure. In many cases, the stored procedure will have parameters you pass it to determine the result set, such as the country abbreviation in the previous examples.

Listing 3.6 is the syntax for a SQL stored procedure. In the SQL Server Enterprise Manager create a new stored procedure in the Northwind database named GetCustomersByCountry.


Listing 3.6 shows a stored procedure called GetCustomersByCountry. This must be added to the Northwind database before the following samples will work.

Listing 3.6 GetCustomersByCountry Stored Procedure for SQL Server Northwind Database

CREATE PROCEDURE[GetCustomersByCountry]
@country varchar (50)
SELECT * FROM Customers WHERE Country = @country

When using a Managed Command to execute a stored procedure you must set the CommandType property. The default value of the CommandType property is Text. To execute a stored procedure you set the CommandType property to CommandType. StoredProcedure and pass in the name of the stored procedure.

Just as classic ADO command objects have a Parameters collection for passing parameters to the stored procedure, ADO.NET Managed Command classes (SqlCommand and OleDbCommand) also have a Parameters collection. You can call to a stored procedure, passing the required parameters in the collection using the following steps:

  1. Create a Managed Command object (SqlCommand or OleDbCommand).

  2. Set the Managed Command's CommandType property to CommandType.StoredProcedure.

  3. Declare a parameter variable (SqlParameter or OleDbParameter).

  4. Add a new instance of the parameter class to the Managed Command's Parameters collection, passing in its name and data type (SqlDbType for SqlParameter and OleDbType for OleDbParameter[ed]See Appendix B for a list of valid SqlDbTypes and OleDbTypes).

  5. Set the parameter's Direction property. (Optional—"Input" is the default.)

  6. Set the Parameter's Value property.

  7. Repeat steps 4-6 for additional parameters.

  8. Execute the Managed Command.

Listing 3.11 demonstrates these steps.


When you're using the SqlCommand object, the names of the parameters added to the Parameters collection must match the names of the markers in the stored procedure. The SQL Managed provider will treat the parameters as named parameters, and it will look for markers in the stored procedure of the same name.

Listing 3.7 Calling a Parameterized Stored Procedure with a SqlCommand


01: <%@ Page Language="VB" %>
02: <%@ Import Namespace="System.Data" %>
03: <%@ Import Namespace="System.Data.SqlClient" %>
04: <script runat="server">
05: Sub Page_Load(Sender As Object, E As EventArgs)
06:  Dim myConnection As SqlConnection
07:  Dim myCommand As SqlCommand
08:  Dim myParameter As SqlParameter
10:  myConnection = New SqlConnection("server=localhost;
   database=Northwind; uid=sa; pwd=;")
11:  myCommand = New SqlCommand("GetCustomersByCountry", myConnection)
12:  myCommand.CommandType = CommandType.StoredProcedure
13:  myParameter = myCommand.Parameters.Add(New SqlParameter("@country",
   SqlDbType.VarChar, 50))
14:  myParameter.Direction = ParameterDirection.Input
15:  myParameter.Value = "USA"
16:  myConnection.Open()
17:  Dim myDataReader As SqlDataReader = myCommand.ExecuteReader()
19:  myDataGrid.DataSource = myDataReader
20:  myDataGrid.DataBind()
22:  myConnection.Close()
23: End Sub
24: </script>


01: <%@ Page Language="C#" %>
02: <%@ Import Namespace="System.Data" %>
03: <%@ Import Namespace="System.Data.SqlClient" %>
04: <script runat="server">
05: void Page_Load(Object sender, EventArgs e){
06:  SqlConnection myConnection;
07:  SqlCommand myCommand;
08:  SqlParameter myParameter;
10:  myConnection = new SqlConnection("server=localhost;
   database=Northwind; uid=sa; pwd=;");
11:  myCommand = new SqlCommand("GetCustomersByCountry", myConnection);
12:  myCommand.CommandType = CommandType.StoredProcedure;
13:  myParameter = myCommand.Parameters.Add(new SqlParameter("@country",
   SqlDbType.VarChar, 50));
14:  myParameter.Direction = ParameterDirection.Input;
15:  myParameter.Value = "USA";
16:  myConnection.Open();
17:  SqlDataReader myDataReader = myCommand.ExecuteReader();
19:  myDataGrid.DataSource = myDataReader;
20:  myDataGrid.DataBind();
22:  myConnection.Close();
23: }
24: </script>

[VB & C#]

25: <html>
26: <head>
27:  <title>Chapter 3: Managed Providers in ADO.NET</title>
28: </head>
29: <form runat="server" method="post">
30: <body>
31: <asp:DataGrid runat="server" id="myDataGrid" />
32: </form>
33: </body>
34: </html>

In Listing 3.7, you create a SqlConnection, SqlCommand, and SqlDataReader, the same as in previous listings. On line 08, you declare a SqlParameter object that will be used to create and add parameters to the SqlCommand. On line 13, you instantiate the SqlParameter object and set its name to @country, which is the same name given to the input parameter in the stored procedure in Listing 3.6. Additionally, you set the data type to SqlDbType.VarChar, 50, as required by the database table. On line 14, you set the SqlParameter's direction to ParameterDirection.Input, and you set the SqlParameter's Value to "USA" on line 15. Lastly, you open the connection and execute the command.


In listing 3.5 you created a series of new DataRow objects, and assigned their values after all the DataRows were created. The same approach can also be used for SqlParameters.

myCommand.Parameters["@country"].Value = "USA";

Input is the default direction for a Managed Command's parameter. There's no need to set a parameter's direction to Input explicitly. Listing 3.7 demonstrated how to set the parameter's Direction property. The possible values are ParameterDirection.Input and ParameterDirection.Output.

  • + Share This
  • 🔖 Save To Your Account

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information

To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.


Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.


If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information

Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.


This site is not directed to children under the age of 13.


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information

If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information

Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents

California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure

Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact

Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice

We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020