- SQL Server Reference Guide
- Introduction
- SQL Server Reference Guide Overview
- Table of Contents
- Microsoft SQL Server Defined
- SQL Server Editions
- SQL Server Access
- Informit Articles and Sample Chapters
- Online Resources
- Microsoft SQL Server Features
- SQL Server Books Online
- Clustering Services
- Data Transformation Services (DTS) Overview
- Replication Services
- Database Mirroring
- Natural Language Processing (NLP)
- Analysis Services
- Microsot SQL Server Reporting Services
- XML Overview
- Notification Services for the DBA
- Full-Text Search
- SQL Server 2005 - Service Broker
- Using SQL Server as a Web Service
- SQL Server Encryption Options Overview
- SQL Server 2008 Overview
- SQL Server 2008 R2 Overview
- SQL Azure
- The Utility Control Point and Data Application Component, Part 1
- The Utility Control Point and Data Application Component, Part 2
- Microsoft SQL Server Administration
- The DBA Survival Guide: The 10 Minute SQL Server Overview
- Preparing (or Tuning) a Windows System for SQL Server, Part 1
- Preparing (or Tuning) a Windows System for SQL Server, Part 2
- Installing SQL Server
- Upgrading SQL Server
- SQL Server 2000 Management Tools
- SQL Server 2005 Management Tools
- SQL Server 2008 Management Tools
- SQL Azure Tools
- Automating Tasks with SQL Server Agent
- Run Operating System Commands in SQL Agent using PowerShell
- Automating Tasks Without SQL Server Agent
- Storage – SQL Server I/O
- Service Packs, Hotfixes and Cumulative Upgrades
- Tracking SQL Server Information with Error and Event Logs
- Change Management
- SQL Server Metadata, Part One
- SQL Server Meta-Data, Part Two
- Monitoring - SQL Server 2005 Dynamic Views and Functions
- Monitoring - Performance Monitor
- Unattended Performance Monitoring for SQL Server
- Monitoring - User-Defined Performance Counters
- Monitoring: SQL Server Activity Monitor
- SQL Server Instances
- DBCC Commands
- SQL Server and Mail
- Database Maintenance Checklist
- The Maintenance Wizard: SQL Server 2000 and Earlier
- The Maintenance Wizard: SQL Server 2005 (SP2) and Later
- The Web Assistant Wizard
- Creating Web Pages from SQL Server
- SQL Server Security
- Securing the SQL Server Platform, Part 1
- Securing the SQL Server Platform, Part 2
- SQL Server Security: Users and other Principals
- SQL Server Security – Roles
- SQL Server Security: Objects (Securables)
- Security: Using the Command Line
- SQL Server Security - Encrypting Connections
- SQL Server Security: Encrypting Data
- SQL Server Security Audit
- High Availability - SQL Server Clustering
- SQL Server Configuration, Part 1
- SQL Server Configuration, Part 2
- Database Configuration Options
- 32- vs 64-bit Computing for SQL Server
- SQL Server and Memory
- Performance Tuning: Introduction to Indexes
- Statistical Indexes
- Backup and Recovery
- Backup and Recovery Examples, Part One
- Backup and Recovery Examples, Part Two: Transferring Databases to Another System (Even Without Backups)
- SQL Profiler - Reverse Engineering An Application
- SQL Trace
- SQL Server Alerts
- Files and Filegroups
- Partitioning
- Full-Text Indexes
- Read-Only Data
- SQL Server Locks
- Monitoring Locking and Deadlocking
- Controlling Locks in SQL Server
- SQL Server Policy-Based Management, Part One
- SQL Server Policy-Based Management, Part Two
- SQL Server Policy-Based Management, Part Three
- Microsoft SQL Server Programming
- An Outline for Development
- Database
- Database Services
- Database Objects: Databases
- Database Objects: Tables
- Database Objects: Table Relationships
- Database Objects: Keys
- Database Objects: Constraints
- Database Objects: Data Types
- Database Objects: Views
- Database Objects: Stored Procedures
- Database Objects: Indexes
- Database Objects: User Defined Functions
- Database Objects: Triggers
- Database Design: Requirements, Entities, and Attributes
- Business Process Model Notation (BPMN) and the Data Professional
- Business Questions for Database Design, Part One
- Business Questions for Database Design, Part Two
- Database Design: Finalizing Requirements and Defining Relationships
- Database Design: Creating an Entity Relationship Diagram
- Database Design: The Logical ERD
- Database Design: Adjusting The Model
- Database Design: Normalizing the Model
- Creating The Physical Model
- Database Design: Changing Attributes to Columns
- Database Design: Creating The Physical Database
- Database Design Example: Curriculum Vitae
- NULLs
- The SQL Server Sample Databases
- The SQL Server Sample Databases: pubs
- The SQL Server Sample Databases: NorthWind
- The SQL Server Sample Databases: AdventureWorks
- The SQL Server Sample Databases: Adventureworks Derivatives
- UniversalDB: The Demo and Testing Database, Part 1
- UniversalDB: The Demo and Testing Database, Part 2
- UniversalDB: The Demo and Testing Database, Part 3
- UniversalDB: The Demo and Testing Database, Part 4
- Getting Started with Transact-SQL
- Transact-SQL: Data Definition Language (DDL) Basics
- Transact-SQL: Limiting Results
- Transact-SQL: More Operators
- Transact-SQL: Ordering and Aggregating Data
- Transact-SQL: Subqueries
- Transact-SQL: Joins
- Transact-SQL: Complex Joins - Building a View with Multiple JOINs
- Transact-SQL: Inserts, Updates, and Deletes
- An Introduction to the CLR in SQL Server 2005
- Design Elements Part 1: Programming Flow Overview, Code Format and Commenting your Code
- Design Elements Part 2: Controlling SQL's Scope
- Design Elements Part 3: Error Handling
- Design Elements Part 4: Variables
- Design Elements Part 5: Where Does The Code Live?
- Design Elements Part 6: Math Operators and Functions
- Design Elements Part 7: Statistical Functions
- Design Elements Part 8: Summarization Statistical Algorithms
- Design Elements Part 9:Representing Data with Statistical Algorithms
- Design Elements Part 10: Interpreting the Data—Regression
- Design Elements Part 11: String Manipulation
- Design Elements Part 12: Loops
- Design Elements Part 13: Recursion
- Design Elements Part 14: Arrays
- Design Elements Part 15: Event-Driven Programming Vs. Scheduled Processes
- Design Elements Part 16: Event-Driven Programming
- Design Elements Part 17: Program Flow
- Forming Queries Part 1: Design
- Forming Queries Part 2: Query Basics
- Forming Queries Part 3: Query Optimization
- Forming Queries Part 4: SET Options
- Forming Queries Part 5: Table Optimization Hints
- Using SQL Server Templates
- Transact-SQL Unit Testing
- Index Tuning Wizard
- Unicode and SQL Server
- SQL Server Development Tools
- The SQL Server Transact-SQL Debugger
- The Transact-SQL Debugger, Part 2
- Basic Troubleshooting for Transact-SQL Code
- An Introduction to Spatial Data in SQL Server 2008
- Performance Tuning
- Performance Tuning SQL Server: Tools and Processes
- Performance Tuning SQL Server: Tools Overview
- Creating a Performance Tuning Audit - Defining Components
- Creating a Performance Tuning Audit - Evaluation Part One
- Creating a Performance Tuning Audit - Evaluation Part Two
- Creating a Performance Tuning Audit - Interpretation
- Creating a Performance Tuning Audit - Developing an Action Plan
- Understanding SQL Server Query Plans
- Performance Tuning: Implementing Indexes
- Performance Monitoring Tools: Windows 2008 (and Higher) Server Utilities, Part 1
- Performance Monitoring Tools: Windows 2008 (and Higher) Server Utilities, Part 2
- Performance Monitoring Tools: Windows System Monitor
- Performance Monitoring Tools: Logging with System Monitor
- Performance Monitoring Tools: User Defined Counters
- General Transact-SQL (T-SQL) Performance Tuning, Part 1
- General Transact-SQL (T-SQL) Performance Tuning, Part 2
- General Transact-SQL (T-SQL) Performance Tuning, Part 3
- Performance Monitoring Tools: An Introduction to SQL Profiler
- Performance Tuning: Introduction to Indexes
- Performance Monitoring Tools: SQL Server 2000 Index Tuning Wizard
- Performance Monitoring Tools: SQL Server 2005 Database Tuning Advisor
- Performance Monitoring Tools: SQL Server Management Studio Reports
- Performance Monitoring Tools: SQL Server 2008 Activity Monitor
- The SQL Server 2008 Management Data Warehouse and Data Collector
- Performance Monitoring Tools: Evaluating Wait States with PowerShell and Excel
- Practical Applications
- Choosing the Back End
- The DBA's Toolbox, Part 1
- The DBA's Toolbox, Part 2
- Scripting Solutions for SQL Server
- Building a SQL Server Lab
- Using Graphics Files with SQL Server
- Enterprise Resource Planning
- Customer Relationship Management (CRM)
- Building a Reporting Data Server
- Building a Database Documenter, Part 1
- Building a Database Documenter, Part 2
- Data Management Objects
- Data Management Objects: The Server Object
- Data Management Objects: Server Object Methods
- Data Management Objects: Collections and the Database Object
- Data Management Objects: Database Information
- Data Management Objects: Database Control
- Data Management Objects: Database Maintenance
- Data Management Objects: Logging the Process
- Data Management Objects: Running SQL Statements
- Data Management Objects: Multiple Row Returns
- Data Management Objects: Other Database Objects
- Data Management Objects: Security
- Data Management Objects: Scripting
- Powershell and SQL Server - Overview
- PowerShell and SQL Server - Objects and Providers
- Powershell and SQL Server - A Script Framework
- Powershell and SQL Server - Logging the Process
- Powershell and SQL Server - Reading a Control File
- Powershell and SQL Server - SQL Server Access
- Powershell and SQL Server - Web Pages from a SQL Query
- Powershell and SQL Server - Scrubbing the Event Logs
- SQL Server 2008 PowerShell Provider
- SQL Server I/O: Importing and Exporting Data
- SQL Server I/O: XML in Database Terms
- SQL Server I/O: Creating XML Output
- SQL Server I/O: Reading XML Documents
- SQL Server I/O: Using XML Control Mechanisms
- SQL Server I/O: Creating Hierarchies
- SQL Server I/O: Using HTTP with SQL Server XML
- SQL Server I/O: Using HTTP with SQL Server XML Templates
- SQL Server I/O: Remote Queries
- SQL Server I/O: Working with Text Files
- Using Microsoft SQL Server on Handheld Devices
- Front-Ends 101: Microsoft Access
- Comparing Two SQL Server Databases
- English Query - Part 1
- English Query - Part 2
- English Query - Part 3
- English Query - Part 4
- English Query - Part 5
- RSS Feeds from SQL Server
- Using SQL Server Agent to Monitor Backups
- Reporting Services - Creating a Maintenance Report
- SQL Server Chargeback Strategies, Part 1
- SQL Server Chargeback Strategies, Part 2
- SQL Server Replication Example
- Creating a Master Agent and Alert Server
- The SQL Server Central Management System: Definition
- The SQL Server Central Management System: Base Tables
- The SQL Server Central Management System: Execution of Server Information (Part 1)
- The SQL Server Central Management System: Execution of Server Information (Part 2)
- The SQL Server Central Management System: Collecting Performance Metrics
- The SQL Server Central Management System: Centralizing Agent Jobs, Events and Scripts
- The SQL Server Central Management System: Reporting the Data and Project Summary
- Time Tracking for SQL Server Operations
- Migrating Departmental Data Stores to SQL Server
- Migrating Departmental Data Stores to SQL Server: Model the System
- Migrating Departmental Data Stores to SQL Server: Model the System, Continued
- Migrating Departmental Data Stores to SQL Server: Decide on the Destination
- Migrating Departmental Data Stores to SQL Server: Design the ETL
- Migrating Departmental Data Stores to SQL Server: Design the ETL, Continued
- Migrating Departmental Data Stores to SQL Server: Attach the Front End, Test, and Monitor
- Tracking SQL Server Timed Events, Part 1
- Tracking SQL Server Timed Events, Part 2
- Patterns and Practices for the Data Professional
- Managing Vendor Databases
- Consolidation Options
- Connecting to a SQL Azure Database from Microsoft Access
- SharePoint 2007 and SQL Server, Part One
- SharePoint 2007 and SQL Server, Part Two
- SharePoint 2007 and SQL Server, Part Three
- Querying Multiple Data Sources from a Single Location (Distributed Queries)
- Importing and Exporting Data for SQL Azure
- Working on Distributed Teams
- Professional Development
- Becoming a DBA
- Certification
- DBA Levels
- Becoming a Data Professional
- SQL Server Professional Development Plan, Part 1
- SQL Server Professional Development Plan, Part 2
- SQL Server Professional Development Plan, Part 3
- Evaluating Technical Options
- System Sizing
- Creating a Disaster Recovery Plan
- Anatomy of a Disaster (Response Plan)
- Database Troubleshooting
- Conducting an Effective Code Review
- Developing an Exit Strategy
- Data Retention Strategy
- Keeping Your DBA/Developer Job in Troubled Times
- The SQL Server Runbook
- Creating and Maintaining a SQL Server Configuration History, Part 1
- Creating and Maintaining a SQL Server Configuration History, Part 2
- Creating an Application Profile, Part 1
- Creating an Application Profile, Part 2
- How to Attend a Technical Conference
- Tips for Maximizing Your IT Budget This Year
- The Importance of Blue-Sky Planning
- Application Architecture Assessments
- Transact-SQL Code Reviews, Part One
- Transact-SQL Code Reviews, Part Two
- Cloud Computing (Distributed Computing) Paradigms
- NoSQL for the SQL Server Professional, Part One
- NoSQL for the SQL Server Professional, Part Two
- Object-Role Modeling (ORM) for the Database Professional
- Business Intelligence
- BI Explained
- Developing a Data Dictionary
- BI Security
- Gathering BI Requirements
- Source System Extracts and Transforms
- ETL Mechanisms
- Business Intelligence Landscapes
- Business Intelligence Layouts and the Build or Buy Decision
- A Single Version of the Truth
- The Operational Data Store (ODS)
- Data Marts – Combining and Transforming Data
- Designing Data Elements
- The Enterprise Data Warehouse — Aggregations and the Star Schema
- On-Line Analytical Processing (OLAP)
- Data Mining
- Key Performance Indicators
- BI Presentation - Client Tools
- BI Presentation - Portals
- Implementing ETL - Introduction to SQL Server 2005 Integration Services
- Building a Business Intelligence Solution, Part 1
- Building a Business Intelligence Solution, Part 2
- Building a Business Intelligence Solution, Part 3
- Tips and Troubleshooting
- SQL Server and Microsoft Excel Integration
- Tips for the SQL Server Tools: SQL Server 2000
- Tips for the SQL Server Tools – SQL Server 2005
- Transaction Log Troubles
- SQL Server Connection Problems
- Orphaned Database Users
- Additional Resources
- Tools and Downloads
- Utilities (Free)
- Tool Review (Free): DBDesignerFork
- Aqua Data Studio
- Microsoft SQL Server Best Practices Analyzer
- Utilities (Cost)
- Quest Software's TOAD for SQL Server
- Quest Software's Spotlight on SQL Server
- SQL Server on Microsoft's Virtual PC
- Red Gate SQL Bundle
- Microsoft's Visio for Database Folks
- Quest Capacity Manager
- SQL Server Help
- Visual Studio Team Edition for Database Professionals
- Microsoft Assessment and Planning Solution Accelerator
- Aggregating Server Data from the MAPS Tool
So far, in covering the process to select data from a database, we've learned to select data, limit the data based on a condition, and group and arrange the data, as well as perform aggregate functions. Here, I'll continue that subject with a new method to apply a condition on the search: the subquery.
A subquery, at its simplest, is just a query in the predicate of another query. Just as with all the constructs we've learned so far, however, simple constructs can form layers that comprise very complicated queries!
Before we get started, we need to clear up some verbiage again, just as we did with the word "query." We've seen, in other tutorials, that sometimes the words used in discussing databases are very specific, and at other times these terms are used interchangeably. To be technical about today's topic, a "subquery" is a selection inside a SELECT statement. A "subselect" is a selection inside an INSERT, UPDATE or DELETE. (More about those later.) In this tutorial, I'll use the term subquery no matter which of these operations we're discussing.
The basic premise to the subquery is quite simple. Subqueries replace various parts of one query with another. To help us through this discussion, we'll look at some concrete examples.
Let's start with the place that the subquery is most often found: in the WHERE section of the selection. Here's a simple query to get us started:
USE pubs GO SELECT au_id, au_fname, au_lname, city FROM authors
Now let's use a subquery to return just the information where the author's state is California. "But wait," you say, "we already know how to do this with a simple WHERE statement." That's true, but to demonstrate this concept, we're going to use a subquery to do the same thing. Here it is:
SELECT au_id, au_fname, au_lname, city FROM authors WHERE state IN ( SELECT state FROM authors WHERE state = 'CA' )
And yes, this is equivalent to:
SELECT au_id, au_fname, au_lname, city FROM authors WHERE state = 'CA'
The reason to look at such a simple example is to show the format and use of the subquery.
The first important thing to notice is the use of the parentheses. Removing them from the statement above produces this error:
Server: Msg 156, Level 15, State 1, Line 3 Incorrect syntax near the keyword 'SELECT'.
The next part of a subquery to pay attention to is the order of evaluation. The WHERE query is evaluated first, which then builds the set that the first query (called the outer query) uses as a condition on the WHERE clause. (If that didn't make sense, read it one more time!)
That example was pretty basic. Let's extend it to do something new.
Subqueries can return any legal value meaning that as long as we get the same data type to compare in the WHERE predicate the query will work.
Also, the subquery doesn't have to work within the same table as the outer query. That means that we can access another table with the second query, and use the results for the condition of the first query.
As a practical example, let's look up all the first and last names of the authors who have published a book.
If we examine the authors table, we see that the publishing information isn't stored there. The pubs database conforms to at least third normal form (see the earlier tutorials about database design) and so the tables are spread out such that repeating data isn't kept together. This means that we'll need to look in a different table (other than authors) to get the published books data, which we find in the titleauthor table. On further examination, we also find that the column that brings the two tables together is au_id.
So using all this information, we need to create a query that finds all the au_id's that have published books, this time from the titleauthor table:
SELECT au_id FROM titleauthor
This query returns the entire set of author IDs from that table. Since this table only stores data if the author has published a book, this is the set of data to use as a limiter for our first table.
Now let's use that set of data to find the author's first and last names in the authors table:
SELECT au_id, au_fname, au_lname FROM authors WHERE au_id IN ( SELECT au_id FROM titleauthor )
And there we have it.
Remember from our previous tutorials that we can also use the NOT operators to filter sets. So, this query would show us the authors who haven't been published yet:
SELECT au_id, au_fname, au_lname FROM authors WHERE au_id NOT IN ( SELECT au_id FROM titleauthor )
We can also use a subquery in the FROM part of the outer query, rather than just in the WHERE section.
For this example, we'll use our layering technique to see the sales of books by store. We'll dissect the query after we run it:
SELECT a.title, COUNT(b.stor_id) FROM titles a, (SELECT title_id, stor_id FROM sales) b WHERE a.title_id = b.title_id GROUP BY a.title ORDER BY COUNT(b.stor_id) DESC
Here's the output:
Is Anger the Enemy? |
4 |
The Busy Executive's Database Guide |
2 |
The Gourmet Microwave |
2 |
You Can Combat Computer Stress! |
1 |
But Is It User Friendly? |
1 |
Computer Phobic AND Non-Phobic Individuals: Behavior Variations |
1 |
Cooking with Computers: Surreptitious Balance Sheets |
1 |
Emotional Security: A New Algorithm |
1 |
Fifty Years in Buckingham Palace Kitchens |
1 |
Life Without Fear |
1 |
Onions, Leeks, and Garlic: Cooking Secrets of the Mediterranean |
1 |
Prolonged Data Deprivation: Four Case Studies |
1 |
Secrets of Silicon Valley |
1 |
Silicon Valley Gastronomic Treats |
1 |
Straight Talk About Computers |
1 |
Sushi, Anyone? |
1 |
There's a lot going on in these four lines, so let's take it a bit at a time.
Take a look at the subquery on the second line: SELECT title_id, stor_id FROM sales). Notice that all we're doing here is getting two pieces of information from the sales table: the title_ids and the stor_ids.
Now, look at the first line of the outer query. Its structure is a bit different than what we've seen before, because there are letters in front of the field names. These letters are called an alias, and tell the query which table the information comes from.
We don't have to use a letter as an alias. We could have spelled out the whole table name (titles.title_id and sales.title_id), but the letters are certainly easier to type.
The reason we haven't seen this construct before now is that this is the first time we've selected two columns from different tables. We're asking for the title from the first table, and the count of the store IDs from the second table. In future tutorials, we'll learn much more about accessing data from several tables at once, but for now we can focus on this method.
In the second line of this query we see the subquery in use. First, we see the titles table and the letter "a" after it. This is how we set up the alias we used in the previous line. Second, we see the subquery asking for the information we need to get the count of stores. Notice also the "b" letter, aliasing the entire subquery.
In the third line we're bringing this all together: the a.title_id = b.title_id WHERE statement. This is the same type of statement we've used in earlier tutorials; it's just that we now include the other table as a limiting condition. It limits the returned sets to those where the two tables have the same values.
Finally, in line four we use the aggregate functions (the ones we learned about last time) to show the number of stores where the books were sold.
So we've seen that the subquery can be used in the WHERE section, in the FROM area, but it can also even be used even in the SELECT part of a query!
Here's a query that shows the author IDs for multiple-author books. Examine it and look for the concepts we've seen so far:
SELECT DISTINCT title_id, (SELECT au_id FROM titleauthor WHERE au_ord = 1 AND title_id = a.title_id), (SELECT au_id FROM titleauthor WHERE au_ord = 2 and title_id = a.title_id), (SELECT au_id FROM titleauthor WHERE au_ord = 3 and title_id = a.title_id) FROM titleauthor a
Here is the result of that query:
BU1032 |
409-56-7008 |
213-46-8915 |
NULL |
BU1111 |
724-80-9391 |
267-41-2394 |
NULL |
BU2075 |
213-46-8915 |
NULL |
NULL |
BU7832 |
274-80-9391 |
NULL |
NULL |
MC2222 |
712-45-1867 |
NULL |
NULL |
MC3021 |
722-51-5454 |
899-46-2035 |
NULL |
PC1035 |
238-95-7766 |
NULL |
NULL |
PC8888 |
427-17-2319 |
846-92-7186 |
NULL |
PC9999 |
486-29-1786 |
NULL |
NULL |
PS1372 |
756-30-7391 |
724-80-9391 |
NULL |
PS2091 |
998-72-3567 |
899-46-2035 |
NULL |
PS2106 |
998-72-3567 |
NULL |
NULL |
PS3333 |
172-32-1176 |
NULL |
NULL |
PS7777 |
486-29-1786 |
NULL |
NULL |
TC3218 |
807-91-6654 |
NULL |
NULL |
TC4203 |
648-92-1872 |
NULL |
NULL |
TC7777 |
672-71-3249 |
267-41-2394 |
472-27-2349 |
The only thing different with this query is that the SELECT values include a subquery. Another construct that might be new is the use of a "self-referencing" query. You might notice that we're only using one table, but we aliased it anyway. That's because we want to compare sets of data from the same table as if there were two tables. By aliasing the table, we can reference it as if there was a duplicate table!
Once again, we've seen a fairly simple concept that has amazing implications. One caveat is important to note: there are performance implications with subqueries. If set up incorrectly, some queries must run for each row that is processed in the outer query.
We'll use the subquery more often with INSERTS, UPDATES, and DELETES when we learn about those in future tutorials.