Home > Articles > Data > SQL Server

📄 Contents

  1. Query Basics
  2. Query Optimization
This chapter is from the book

Query Optimization

Now that you have query syntax in hand, it's time to create the query. It's at this point when you should think about optimization. Many times it's tempting to "just get the query out there" and then reevaluate it to make it faster. The issue is that far too often you'll forget to come back and correct the query. Even worse, if you create the query incorrectly you might cause related performance issues that are difficult to detect.

So how do you identify an inefficient query? First, you need to understand the route the query takes to satisfy the results. The route includes the various methods the SQL Server engine uses to locate the rows of data, whether that means reading a table from beginning to end or the indexes the query uses. This route is called a "query execution plan." Microsoft SQL Server provides three tools to evaluate a query and the query plan. Two are available inside Query Analyzer and the other is in the SQL Server Profiler tool.

The two methods inside the Query Analyzer tool include a graphical query plan and a text display of that plan. I'll start with the graphical tool and then examine the text you can receive from Query Analyzer, and then I'll explain how to use SQL Server Profiler to see the execution plan as well.

I'll begin by opening Query Analyzer and connecting to the pubs database. Once there, I type a simple query:

SELECT *
FROM authors
GO

Before I run the query, however, I'll select Show Execution Plan from the Query menu, as shown in Figure 7.1.

One thing before I actually run the query—you can also choose to display an estimated execution plan. This means the system will attempt to predict what might happen as far as the path goes. I don't use this option very often, since there's rarely a reason to do so. Some might argue that a particular query might take too long to run. My pushback to that is that a developer should be working on a development system—preferably a virtual system anyway. So who cares if it takes a while? The other reason I don't use this option is that if your query creates temporary tables it won't display the plan; since the query doesn't really run, it doesn't create the temp tables, and there you are.

Getting back to my example, I press F5 to run the query, and I get the results. I also get an additional tab in the results pane, where you can see the graphical representation of the query plan (see Figure 7.2).

There's quite a bit of information, even in this small display. You read the plan from right to left. If the query is complex, you'll see a lot of information— I recommend you split the larger query into smaller ones until you know what they are doing, and then put them back together a little at a time.

You can see two icons which display the operations the engine used to get the data. I've clicked on one of them and that graphic then displays more detail about that operation.

Notice also the small arrow pointing to the left. It's a small arrow because the operation wasn't that time consuming. You'll notice on larger queries that this arrow will be much thicker. Small clues like that make this a powerful tool.

For instance, if the icon turns red it indicates that the operation could benefit from statistics. Just right-click that red icon and you can create the statistics on the fly! Also—try moving your cursor over the direction arrows. You'll get the number of records that were transferred in that step.

You'll also see within the information box the CPU and I/O costs. Don't put too much stock in the numbers themselves—they just help the query optimizer create a total cost for the query, and don't reflect real world CPU ticks.

Look for the operations that have the highest cost. Those are the steps you want to attack first.

This particular query used a clustered index scan, which means that the query processor satisfied the query by reading all the rows in order from the index, which is really the table. In the case of a clustered index, the data is physically stored in the order of the index, so reading that index turned out to be 100% of the cost of the query. The icon showing a tree of computers with a blue arrow indicates the clustered index scan.

An index scan isn't a great thing—I can do better (see Figure 7.3).

That is better—look closely at the graphics. This time I got an Index seek instead of an Index scan. That's an important distinction—a scan means that the system had to read through all the rows to get the data it was looking for. A seek means that the query processor was able to find what it needed directly from the pointers in the index.

It's similar to having to look through the whole house to find your keys versus knowing to look on the dresser. The reason I'm doing better now is that I've added a WHERE clause. Getting just the data I need makes use of the index properly. As a matter of fact, without an index, you're more often than not going to receive a table scan, which is usually quite bad.

I say usually, because in some cases it's faster for SQL Server to read an entire table than it is to use an index. This is normally the case for any small table, saw below a few hundred rows or so.

I've still got an issue, though, because now I have a Bookmark Lookup icon as well. As a matter of fact, it's half the cost of the entire query. A Boomark Lookup means the system found the rows quickly, but then had to find which columns to bring back. The reason this happened with my query is that I used a SELECT* statement (which you should never do in production). This means all columns, and some aren't covered by the index, so it had to get the columns from the table rather than the index. While this brings back all the columns without my having to bother with figuring out which ones I want, it's very inefficient.

I'll go back to the program to see what's really needed, and I find that I only really want the last name of the author (see Figure 7.4).

That's better. In fact, it doesn't get any better than this. A 100% index seek is exactly what you're after—if you can get it.

You can use Books Online to find the other query plan symbols and what they mean—just look up the topic Graphically Displaying the Execution Plan Using SQL Query Analyzer. Here are the ones to watch out for:

  • Index or table scans. As I mentioned, if you're getting a scan, the system has to read the entire table to find the data. You should look for an index to make the query more useful, or consider creating one.
  • Sort. A sort happens when you use an ORDER BY on the query. If you need the data in that order, fine. If it's not necessary, however, consider leaving it out.
  • Bookmark lookup. As I mentioned earlier, these are often caused by using a SELECT* statement. There is almost never a reason to do this in production systems.
  • Filter. This one is a bit trickier. You'll often see these when you use a function, which are sometimes the best way to get the data. Again, see if you can reconstruct the query to use an index or create one if possible.

There's a textual representation of this kind of data available as well. Just type:

SET SHOWPLAN_TEXT ON

And you'll see it. The information is largely the same, but to be honest, the graphical method is best. I'm normally very biased towards command-line operations, but in this case, the graphical plan really does show you more information quickly.

Finally, there's another method to see the query plans. You can use the SQL Server Profiler tool—just capture these events:

Performance: Execution Plan
Performance: Show Plan All
Performance: Show Plan Statistics
Performance: Show Plan Text
And then pick these data columns:
Start Time
Duration
Text data

You might want to limit the duration to the larger queries so that you don't get inundated with data.

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