Home > Articles > Data > SQL Server

In-Process Data Access in SQL Server 2005

Whether you access data from the client, middle tier, or server, when you’re using SQL Server and the .NET Framework, you use the SqlClient data provider. Your data access code is similar regardless of its location, but the .NET Framework 2.0 version of SqlClient contains code to encapsulate differences when you’re programming inside SQL Server and optimize the in-server programming environment. This chapter introduces you to the idea of in-process data access.
This chapter is from the book

Whether you access data from the client, middle tier, or server, when you’re using SQL Server and the .NET Framework, you use the SqlClient data provider. Your data access code is similar regardless of its location, but the .NET Framework 2.0 version of SqlClient contains code to encapsulate differences when you’re programming inside SQL Server and optimize the in-server programming environment.

Programming with SqlClient

Accessing data from outside SQL Server entails connecting to SQL Server through a network library and a client library. When you use the .NET Framework with SQL Server, you use System.Data.dll as the client library and the ADO.NET programming model. ADO.NET is a provider-based model, similar in concept to ODBC, OLE DB, and JDBC. The model uses a common API (or a set of classes) to encapsulate data access; each database product has its own provider. ADO.NET providers are known as data providers, and the data provider for SQL Server is SqlClient. The latest release of SqlClient, installed with .NET Framework 2.0, includes new client-side functionality to take advantage of new features in SQL Server 2005. In addition, SqlClient contains extensions to allow ADO.NET code to be used inside the database itself. Though T-SQL is usually preferred when a stored procedure, user-defined function, or trigger accesses database data, you can also use ADO.NET when writing procedural code in the .NET Framework. The programming model when using SqlClient in .NET Framework stored procedures is similar to client-side code but in-database access is optimized because no network libraries are needed. Let’s start by writing some simple client database code and then convert it to run on the server.

Simple data access code is very similar regardless of the programming model used. To summarize, using ADO.NET and SqlClient as an example:

  1. Connect to the database by instantiating a SqlConnection class and calling its Open method.
  2. Create an instance of a SqlCommand class. This instance contains a SQL statement or procedure name as its CommandText property. The SqlCommand is associated with the SqlConnection.
  3. Execute the SqlCommand, and return either a set of columns and rows called SqlDataReader or possibly only a count of rows affected by the statement.
  4. Use the SqlDataReader to read the results, and close it when finished.
  5. Dispose of the SqlCommand and SqlConnection to free the associated memory, network, and server resources.

The ADO.NET code to accomplish inserting a row into a SQL Server table would look like Listing 4-1.

Listing 4-1: Inserting a row using SqlClient from the client

// Code to insert data from client
//  See chapter 14 for an implementation of
//  the GetConnectionStringFromConfigFile method.
string connStr = GetConnectionStringFromConfigFile();
SqlConnection conn = new SqlConnection(connStr);
conn.Open();
SqlCommand cmd = conn.CreateCommand();
cmd.CommandText = "insert into test values (’testdata’)";
int rows_affected = cmd.ExecuteNonQuery();
cmd.Dispose();
conn.Dispose();

The previous ADO.NET code ignored the fact that an exception might cause the execution of cmd.Dispose or conn.Dispose to be skipped. The preferred and simple way to prevent this from happening is to use the using syntax in C#. One or more object instance declarations are followed by a block of code. The Dispose method is called automatically at the end of the code block. We’ll be using the using construct a lot in the code in this book. Rewritten using this syntax, the code above would look like Listing 4-2.

Listing 4-2: Inserting a row using SqlClient from the client, C# using construct

//code to insert data from client
string connStr = GetConnectionStringFromConfigFile();
using (SqlConnection conn = new SqlConnection(connStr))
using (SqlCommand cmd =
 new SqlCommand("insert into test values (’testdata’)", conn))
{
 conn.Open();
 int rows_affected = cmd.ExecuteNonQuery();
} // Dispose called on cmd and conn here

Other classes in a typical ADO.NET data provider include a transaction class (SqlTransaction) to tie Connections and Commands to a database transaction, a parameter collection (SqlParameterCollection) of parameters (SqlParameter) to use with parameterized SQL queries or stored procedures, and specialized Exception and Error classes (SqlException, SqlErrorCollection, SqlError) to represent processing errors. SqlClient includes all the typical classes; Figure 4-1 shows the object model.

Figure 4-1

Figure 4-1 The SqlClient provider object model (major classes only)

The same basic model is used inside the server to access data in .NET Framework stored procedures. It’s familiar to ADO.NET programmers, and using it inside the server makes it easy for programmers to use their existing skills to write procedures. The big difference is that when you’re writing a .NET Framework procedure, you’re already inside the database. No explicit connection is needed. Although there is no network connection to the database, there is a SqlConnection instance. The difference is in the connection string. Outside the database, the connection string should be read from a configuration file and contains items like the SQL Server instance to connect to (server keyword), the SQL Server login (either User ID and Password keywords or Integrated Security=true), and the initial database (database keyword). The connection string that indicates to SqlClient that we’re already inside the database and the provider should just use the existing database context contains only the keyword "context connection=true". When you specify "context connection=true", no other connection string keyword can be used. Listing 4-3 is the same code as above but executing inside a .NET Framework stored procedure.

Listing 4-3: Inserting a row using SqlClient in a SQLCLR stored procedure

//code to insert data in a stored procedure
public static void InsertRowOfTestData()
{
 string connStr = "context connection=true";
 using (SqlConnection conn = new SqlConnection(connStr))
 using (SqlCommand cmd =
  new SqlCommand("insert into test values (’testdata’)", conn))
 {
  conn.Open();
  int rows_affected = cmd.ExecuteNonQuery();
 }
} 

Note that this code is provided as a stored procedure only to explain how to access data on the server. Not only is the code faster as a Transact-SQL (T-SQL) stored procedure but also SQL Server will check the SQL statements for syntactic correctness at CREATE PROCEDURE time. This is not the case with the .NET Framework stored procedure above. When you execute SQL statements by using SqlCommand, it’s the equivalent of using sp_executesql (a system-supplied store procedure for dynamic string execution of commands) inside a T-SQL stored procedure. There is the same potential for SQL injection as with sp_executesql, so don’t execute commands whose CommandText property is calculated by using input parameters passed in by the procedure user.

This code is so similar to the previous client-side code that if we knew whether the code was executing in a stored procedure on the server or on the client, we could use the same code, changing only the connection string. But a few constructs exist only if you are writing server-side code. Enter the SqlContext class.

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.

Overview


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.

Surveys

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.

Newsletters

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.

Security


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

Children


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

Marketing


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.

Choice/Opt-out


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.

Links


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