SQL Server Reference Guide

Mar 28, 2003

␡

⎙ Print

< Back Page 165 of 365 Next >

Have you ever wondered exactly how SQL Server "answers" a query? By that I mean the process that the SQL Server engine uses to get the data or perform the command you've typed in.

In other articles I've explained how you can use tools such as SQL Server Profiler and the graphical and textual Showplan to watch the steps that SQL Server takes to work with data and data structures. But the fact that there is an engine within SQL Server that processes your commands and requests is only part of the story.

It wouldn't be too difficult to write a program that takes input, stores it, and retrieves or alters it. If you've ever written any code at all, you've probably written a program that does something similar to what a database does. So simply taking in some data and retrieving it again, isn't the magic that an enterprise-scale system provides. The real power and value of a database system is a mechanism that performs these tasks quickly. In SQL Server, that mechanism is the Optimizer.

The Optimizer intercepts all calls to the SQL Server engine and determines the best way to get to the data or implement the command. It does this by using a number of metrics and measurements and adding them up into a "cost". The Optimizer works far quicker than any human could, and it contains more logic and cost information that you or I could calculate. What that means is that in almost every case, the Optimizer will pick the "right" thing to do.

Almost every case. Sometimes you evaluate a Showplan output, and you just can't figure out why a certain index isn't being used, or you think that a particular path to the data might make more sense.

Before we start, it's important to understand that before you force a query with a hint, you should tell yourself that you're probably wrong. You should almost never put these hints on, and if you do, you should understand what the implications are. The Optimizer can see more activity on the server than you can, so it might make one query suffer to enhance the overall performance of the system. Also, if you do put these hints in your code, make sure you note that change and review it after each system change or service pack installation. As things change, the performance of the statements may change. If you're doing performance tuning on a system, these hints are prime places to evaluate for problems.

Note also that even with the Hint, the Optimizer might choose another path. For instance, you might set a certain index to be used, but the Optimizer might find that using it would be a real problem.

Types of Hints

Technically, all of the hints I'll explain in this tutorial are called "Optimizer Hints". The reason is that the Optimizer is what is affected by the Hint, regardless of what object it acts on. There are other types of hints, such as Query Hints, which I'll cover later.

Table/Lock Hints

I've actually covered a few of these Hints already, although not all of them, in another tutorial. I'll cover these first since I think that these are the most useful — something you'll have the best luck with.

Table hints, and specifically lock hints, affect the most common Data Manipulation Language statements, including SELECT, INSERT, UPDATE and DELETE. As I did with the locking hints, let's cover a few of the table hints.

Again, you'll use these in the statements I mentioned above. As an example, let's take a look at a sample SELECT query that you want to force a certain index on:

SELECT Fname 
FROM Customers
WITH (INDEX(FirstNames_idx))

That query, from a fictional table called Customers, would return the FName field. But the key is the bottom part, where the code tells the Optimizer to use an index called FirstNames_idx.

So with that in mind, let's take a look at a few of the ones that I've found useful. First, here's the full list of Table Hints from Books Online:

FASTFIRSTROW	READCOMMITTEDLOCK
HOLDLOCK	READPAST
IGNORE_CONSTRAINTS	READUNCOMMITTED
IGNORE_TRIGGERS	REPEATABLEREAD
INDEX	ROWLOCK
KEEPDEFAULTS	SERIALIZABLE
KEEPIDENTITY	TABLOCK
NOLOCK	TABLOCKX
NOWAIT	UPDLOCK
PAGLOCK	XLOCK
READCOMMITTED

To narrow the list a bit, let's start with the locking hints I mentioned in the previous article.

READUNCOMMITTED

This hint sets an "isolation level", which has to do with locking. When you set this hint in your query, you can actually read rows that have been changed in another query, but have not yet been committed to the database.

READCOMMITTED

The opposite of the one we just saw — and the default for SQL Server queries. It means that if the data hasn't been written to the database yet, you won't be able to read it until it is.

REPEATABLEREAD

Blocks reads and writes of uncommitted data.

SNAPSHOT

Similar to READUNCOMMITTED, it allows "dirty reads". It's actually even a little more "dirty". You'll have to enable the database option of ALLOW_SNAPSHOT_ISOLATION to use it.

SERIALIZABLE

This hint combines SNAPSHOT and READCOMMITTED, which has the effect of making the data "stable" through the whole query. The downside is that it takes a lot of locks.

Now let's take a look at a few of the other interesting hints. These may have indirect effects on locks, but not as much as the hints we just talked about.

INDEX (indexname, indexname, indexname,...)

This is the hint I pointed out earlier. It asks the optimizer to consider a certain index on a table. While this can be useful, I've found it to be one of the most over-used hints out there. Again, you normally can't out-guess the optimizer!

IGNORE_CONSTRAINTS/IGNORE_TRIGGERS

I mention this hint not because you want to use it, but because you probably won't. From the name, you might think that this helps you because you could insert data and ignore primary and foreign keys, or triggers — and that's partly true. But in reality, you can only use this hint when you're doing a Bulk Insert using the OPENROWSET option, and even so you'll have to deal with these issues later.

KEEPIDENTITY

This hint is one I have used. It has to do with an Identity field, which is a field that is automatically assigned a sequential number by SQL Server. Sometimes, to maintain referential integrity, I need to bring data from one table that has an Identity field to another table that also has the Identity field turned on, often in another database.

What this hint does is allow you to "suspend" the Identity function during and import, keeping the old value (the original from the source table) instead of using the new one from the destination table to be used. You do need to make sure they won't clash, but at least you can keep the old numbers.

Once again, during your INSERT statement you need to have the BULK option used with the OPENROWSET function to make this work.

So there you have it. A series of hints that you can use to help you make things happen on the server the way you want them to. I'll state it once again – you probably don't want to use any of these hints, unless you've taken the time to understand the effects they have on your system. If you do use them, create documentation that states why and where, and then review them constantly, especially after a Service Pack or upgrade.

InformIT Articles and Sample Chapters

Although I've got a great performance tuning section in the database guide, you should also check out this free book excerpt.

Books and eBooks

If you want a full reference on SQL Performance Tuning, check out this book.

Online Resources

Always one of my favorites, the SQL Server Performance Tuning articles here also cover the optimizer.

< Back Page 165 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