SQL Server Reference Guide

Mar 28, 2003

␡

⎙ Print

< Back Page 92 of 365 Next >

As I’ve described in other overviews and tutorials, SQL Server handles locking, blocking and deadlocking automatically. But you can actually cause or fix locks using three control levers. In this tutorial I’ll show you how to do just that.

As a refresher, all Relational Database Management Systems (RDBMS) have locks. They are integral to the operation of the system, primarily to ensure data integrity. You have to guarantee that while a user or even an operation reads data, the data shouldn’t be allowed to change. That of course goes double for changes to the data — which in fact involves a read operation first.

In the last tutorial of this series I explained how you can discover and view the locking activity on your databases. In this tutorial I’ll show you how to mitigate, or deal with them.

Controlling Locking Behavior Using Proper Design

The first and most basic thing you can do to deal with locks is to create a design that minimizes them as much as possible. Interestingly, even though it is simple to design good locking behavior at the start of your application this is one of the most difficult tasks to do later. Once you have a design, it is very painful to evaluate it as the cause of a locking problem, and it can be almost impossible to take the system apart to fix it once there is data in the tables.

Let’s look at a concrete example. In the AdventureWorks database in SQL Server 2005, there are several tables that deal with inventory for a bicycle shop. Some of these data elements are the item name, its type, and its location, how many are on hand and in some cases even a picture of the item.

At first glance it makes sense to create a table with all of this information. After all, we normally think of the data as the end result — what it would look like in an application or a report on the screen. But what you need to consider is how the data will be used. The location, for instance, will be set up by plant managers and manufacturing divisions and the image of the item will probably be handled by marketing or even engineering. Sales will want to query the amount of items, but both sales and manufacturing will change the number. If all of these applications have to look in the same table and even row for a piece of data, then the system will have to lock that row to prevent one application from reading a datum that has changed — called a "dirty read." The more groups of people need to look at or change an atomic value (such as the quantity) the more you should separate those data elements out to other tables. This is called normalization, and I’ve covered it in another article here on InformIT.

So as you can see, the design of the database is the first place to start in dealing with locks. It’s mostly trivial for a database engine to join several tables together, so you don’t pay an extremely large penalty for having more tables rather than fewer. And, you let one function access only the data they care about long enough to read or make changes.

If you follow the process I detailed in the normalization article, you’ll have a good start on the design as far as locks go. The important thing to remember is to think about how the system will be used when you design the tables.

Controlling Locking Behavior Using Timeouts

The next lever you have for controlling locks is using timeouts. This sets how long a query will wait for a blocked resource. If you have a suspicion that there will be a lot of locking for a particular column, you can code your application to only wait a few seconds on the resource before it either tells the user that the resource is unavailable, or you can have the application retry the query a bit later to avoid the lock. Your application will still slow down a bit if the locks occur, but at least this way you don’t escalate the locks so quickly and you’re in charge of how long the process takes. People dislike waiting, but they really dislike it when the application appears to "freeze".

You can change the timeout behavior in a couple of ways, but the simplest is to use the @@LOCK_TIMEOUT function in your code. You just specify the timeout value in milliseconds at the top of the batch that you run:

SET LOCK_TIMEOUT 1800
SELECT * FROM Inventory;
GO

Controlling Locking Behavior Using Isolation Levels

Most of the time you’ll want to leave SQL Server alone to deal with locks, since it will handle that automatically. But in some circumstances you’ll want to control the type of locking that your query will take. You may decide that it’s more important to read the data quickly, even if it might be subject to change in a moment. You can control the type of lock, and even how long it will be taken using Transaction Isolation Levels.

Note that no matter what you do with these Isolation Levels, data changes always get an exclusive lock. You’d lose data integrity if they didn’t.

You control the Transaction Isolation Level with the SET TRANSACTION ISOLATION LEVEL statement. It takes one of the following parameters, which I’ll explain inline.

READ UNCOMMITTED

This Isolation Level allows your query to read rows that have been changed by another transaction, but hasn’t yet been committed to the database. What this means is that they don’t issue a SHARED lock, meaning other queries don’t know that it isn’t in there working away. Using this Isolation Level, you can get those "dirty reads" I mentioned earlier. Sometimes that’s alright, but normally this isn’t what you’re looking for.

This Isolation Level also doesn’t block a system from updating a piece of data it has — once again, as long as it isn’t committed yet. When data is being committed, it always gets an exclusive lock.

This Isolation level will also allow "phantom reads," meaning that by the time the query finishes, there might not be as many rows in the table as what was returned. Let’s say you have the values 1 through 1,000,000 in a table. With this Isolation Level you can’t always be sure someone won’t delete row 9,000 before you finish reading it, so you can see data in the application that no longer appears in the database.

READ COMMITTED

This is the default Isolation Level of SQL Server, and it basically says that queries can’t read data that has been changed but not yet committed by other queries. It’s one of the "safest" Isolation Levels.

REPEATABLE READ

This is one of the most restrictive Isolation Levels in a transaction. It says that queries can’t read data that has been changed but not yet committed by another query. Also, other queries can’t change any of the data that has been read by the transaction until it finishes.

SNAPSHOT

This Isolation Level is similar to READ UNCOMMITTED, since it allows a complete data read without locks. What that means is that the data you see in the application is what it was when you started the query.

To use this level, you have to set a database option called ALLOW_SNAPSHOT_ISOLATION to be ON.

SERIALIZABLE

This hybrid type of Isolation Level sort of combines SNAPSHOT and READ COMMITTED — it says that even if you repeat the query, you’ll get the same data, at least in the same transaction. It also does a lot of blocking, so use it with care.

You can use any of these strategies to deal with your locking issues. I recommend that you leave the defaults for SQL Server locking, and let the engine take care of the proper levels and timeouts. But if you use the monitoring processes and tools I mentioned in my previous article and find locks to be a problem, then you should investigate these methods and test them on your development server.

InformIT Articles and Sample Chapters

Kevin Kline explains how you can write code to minimize locking here.

Online Resources

There is a lot more here about concurrency (which is basically locking) here.

< Back Page 92 of 365 Next >

🔖 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.

Privacy Notice

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

Email Address