- 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
In most programming constructs that somehow map to T-SQL, such as loops, we have to be pretty liberal in our comparisons. T-SQL simply doesn't implement some programming language concepts very well. In others, however, T-SQL actually shines. Using T-SQL, we can write things that aren't available easily in other languages. One such construct is the Array.
An array is a simple enough idea: it's a single variable that acts a bit like a spreadsheet. To understand why you might want to use an array, think of a box of chocolates. When you bring them into the office to share, you bring the entire box not the individual pieces. However, when you eat the chocolate, there are many different pieces inside. Everyone seems to like different kinds of chocolate. One person picks the cream-filled, another picks the toffee.
That's how an array works. To stretch the analogy a bit, the box is the variable, and the individual chocolates are the "cells" of the array.
To create an array in a high-level programming language, you declare it first, often setting the number of rows and columns it contains. After that, you can fill each cell with values. From there, you refer to the cell by the variable name, followed by the row and column number. Here's a grid of 2 by 2 cells created in Visual Basic, for instance:
Dim grid(2,2) As String
Here, "grid" is the variable name, and it has 2 columns and 2 rows. Here's how you put the value "Toffee" the bottom right cell:
Grid(2,2) = "Toffee"
And you could see the contents of the first cell at the bottom this way:
Print Grid(2,1)
There are other types of arrays, such as ragged, dynamic, and multi-dimensional. You can also create an array that has just one row, and several columns, which is a common way to store things like a range of dates.
There are lots of reasons to use arrays, such as calendars and lists. Just about any grouping of data fits an array.
SQL Server tables are also a kind of array. They are two-dimensional storage places for data, and you can access any discrete cell in them. The difference is that they are persistent, or permanent. You don't normally use them as a variable.
There are times, however, when you need an array variable in your T-SQL code. While T-SQL doesn't have an array variable type, it actually has something a little better: Table Variables.
Table variables are just what they sound like a variable that holds a table. Here's an example of how to create one:
DECLARE @VariableName TABLE ( Field, FieldType NOT NULL ,...)
The great thing about these variables is that they're handled in memory. Of course, that also means that you've got to be careful with them, since you can bog down your machine if they get too large.
Most often, you'll use table variables to hold little bits of information that you need throughout a stored procedure. They are very handy to hold a set of comparison or update values. Let's take a look at an example:
DECLARE @FirstLastAuthors TABLE ( AuthorName varchar (50) NOT NULL , State char(2) NOT NULL )
Notice that I declared a variable name, and gave it a TABLE type. Inside the parentheses I followed standard T-SQL syntax for creating a table. There are a few limits here, so it's important to use a table variable for small, discrete data sets. I've posted a few references at the end of this article to explain more about these limits, but basically if you find yourself wanting to put an index on a table variable, the data is probably too large for a table variable.
Table variables are also used to store transformed data to use in another query. Table variables are also used to form the basis for an UPDATE statement as a set of comparison values.
Now that I've created the table variable, I can fill it with the values I want. In this example, I'll transform the au_fname and au_lname fields from the pubs database into a single field in the last-name, first-name format. To work with the table variable, I treat the variable name like a regular table:
INSERT INTO @FirstLastAuthors SELECT au_lname + ', ' + au_fname, state FROM authors ORDER BY state
Now that I have values in the table, I can query them to see what they look like.
SELECT * FROM @FirstLastAuthors -----------------------------------
White, Johnson |
CA |
Green, Marjorie |
CA |
Carson, Cheryl |
CA |
O'Leary, Michael |
CA |
Straight, Dean |
CA |
Bennet, Abraham |
CA |
Dull, Ann |
CA |
Gringlesby, Burt |
CA |
Locksley, Charlene |
CA |
Yokomoto, Akiko |
CA |
Stringer, Dirk |
CA |
MacFeather, Stearns |
CA |
Karsen, Livia |
CA |
Hunter, Sheryl |
CA |
McBadden, Heather |
CA |
DeFrance, Michel |
IN |
Smith, Meander |
KS |
Panteley, Sylvia |
MD |
del Castillo, Innes |
MI |
Blotchet-Halls, Reginald |
OR |
Greene, Morningstar |
TN |
Ringer, Anne |
UT |
Ringer, Albert |
UT |
Remember that variables in T-SQL are all local you can't create a variable in one batch and "see" it in another. It is destroyed as soon as you run the batch. That means that all three statements from above have to be run together to work. If you run them separately, you'll get an error message.
In addition to table variables, T-SQL allows you to create another array substitute: the temporary table. I mentioned these kinds of tables briefly in my article on statistics. A temporary table is constructed the same way as any other table in SQL Server, but you preface the table name with a pound sign (#). Once the temporary table is created, it is stored in tempdb until you break the connection (not the batch). When you terminate the connection, the temporary table is destroyed. This type of table is called a local temporary table.
Each stored procedure is a complete connection, so if you're creating the temporary table in a stored procedure, it is destroyed when the stored procedure completes.
Another type of temporary table, called a global temporary table, isn't destroyed when the connection is broken. The global temporary table is retained until the last connection references it. In effect, this is the closest you can get to a global variable in T-SQL. You create a global temporary table by prefacing the table name with two pound signs (##).
Here's the same code we saw earlier in the table variable explanation, this time using a local temporary table:
CREATE TABLE #FirstLastAuthors ( AuthorName varchar (50) NOT NULL , state char(2) NOT NULL ) INSERT INTO #FirstLastAuthors SELECT au_lname + ', ' + au_fname, state FROM authors ORDER BY state
Since I haven't closed my Query Analyzer connection yet, I can query the temporary table later, unlike a table variable.
SELECT * FROM #FirstLastAuthors
While temporary tables are very useful, table variables do still have a few advantages. For one thing, they are run in memory, so they are very fast. They aren't written to tempdb, as are temporary tables, so they don't punish the I/O subsystem.
In addition to table variables and temporary tables, you can simulate an array with a User Defined Function (UDF) that returns a table. Here's a sample of that syntax:
USE pubs GO CREATE FUNCTION dbo.SimpleTableFunction(@LastName varchar(50)) RETURNS TABLE AS RETURN SELECT * FROM employee WHERE au_lname LIKE @LastName
The function is permanent, but doesn't store the table data. In a way, it's similar to a view.
The advantage of this type of array is that you can pass the function a variable, as you can see above. Of course, you can have the UDF perform a lot more logic if you need it.
To access the data in this UDF, I'll pass the variable of the last name I'm looking for to the function by using a SELECT statement:
SELECT * FROM SimpleTableFunction('White') -----------------------------------
172-32-1176 |
White |
Johnson |
408 496-7223 |
10932 Bigge Rd. |
Menlo Park |
CA |
94025 |
1 |
We'll talk more about UDF's in future articles.
To decide when to use each type of array, make an evaluation of the purpose of the array. If you need a quick, in-memory set of values, use a table variable. To use a larger set of data that is visible to more than one connection, use a temporary table. To pass variables to the array, use a User Defined Function.
Online Resources
In this article, Peter Bromberg that describes table variables a little further, and shows how to use them in place of a cursor.
Microsoft explains table variable advantages and limitations in this article on their support site.
InformIT Tutorials and Sample Chapters
Baya Pavliashvili has a great article on the merits of UDFs.