- 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
We've been exploring SQL Data Management Object (SQL-DMO) programming in our last few articles. If you're just joining us, you might want to read the previous two articles to bring you up to where we are today.
The program we have so far uses the SQLServer object. This object has been around for quite a while, all the way back to SQL Server version 7. In SQL Server 2000, the DMO model was extended to have even more properties and a few more methods. Instead of changing the SQLServer object, Microsoft added another object: SQLServer2. This object "inherits" all the things that the SQLServer object can do. From here on, I use the SQLServer2 object, but if you're running SQL Server version 7 you'll need to stick with the older object.
I'll need to change my comments to reflect these changes, so here's how the code looks now:
' dmo.vbs ' Created: 12/10/04 - Buck Woody ' Change Log: '12/11/04 - Buck Woody - Added comments, InputBox. '12/17/04 - Buck Woody - Changed Server object to 'SQLServer2 and added two new properties to show ' Variable to hold Server Name Dim ServerNameVar ' Variables for the text boxes Dim MsgBoxVar Dim MsgTxtVar ' Ask for the name ServerNameVar = InputBox("Enter Server Name:") If ServerNameVar = "" Then ServerName = "(local)" End If ' Create the server object using SQL-DMO Set oServer = CreateObject("SQLDMO.SQLServer2") ' Login with current Windows account oServer.LoginSecure = True oServer.Connect ServerNameVar ' Fill the variable with server properties MsgTxtVar = "Name: " & oServer.Name & VbCRLf _ & "ANSI Nulls: " & oServer.AnsiNulls & VbCRLf _ & "Host: " & oServer.HostName & VbCRLf _ & "Service Name (2): " & oServer.ServiceName & VbCRLf _ & "Auto-Start (2): " & oServer.AutoStart & VbCRLf _ & "Version: " & oServer.VersionMajor & "." _ & oServer.VersionMinor & VbCRLf _ & oServer.VersionString ' Get the message box MsgBoxVar = MsgBox(MsgTxtVar, 64, "SQL Server Info") ' Clean up Set oServer = Nothing
This is a bit better, since I now have access to a few more properties, but the program still doesn't do very much. In this article, I extend its functionality to do a shutdown of the SQL Server service on that system.
To accomplish that I use a method. By now, you'll remember that the SQL-DMO library gives us access to properties (settings to set and display) and methods (actions to perform). A method is simple enough to call. It's similar to what I've already shown you with properties; you just preface the method with the object name. The method may require various parameters, depending on what it does. I'll show you a few of those as we move along, and you can always refer to the Microsoft reference site for the full listing.
The .Shutdown method has only one parameter: Wait. This parameter can be either TRUE or FALSE, and it's optional. If Wait is set to TRUE (the default) then the server performs a clean, orderly shutdown. If Wait is set to FALSE, then the service shuts down no matter what.
NOTE
If a parameter is used, you have to put it in between parenthesis. If you don't use a parameter, you don't need them.
So to shutdown a server is nothing more than this line:
oServer.Shutdown
That's fine, but it might be better to offer the user a chance to request that shutdown, just in case they don't know what the program does when they start it. To do that, we need to get more input from the user. We could use another variable, but in this case I'll just use the built-in functionality of the MsgBox() function in VBScript.
Recall that I set the type of the message box with a number in this line:
' Get the message box MsgBoxVar = MsgBox(MsgTxtVar, 64, "SQL Server Info")
The "64" sets the box to "information." Other numbers set the box to do more things. You can also use words (called vb-constants) instead of the numbers, so we'll do that for better readability. Here's a handy chart:
VBOKOnly |
0 |
Show OK button |
VBOKCancel |
1 |
Show OK and cancel buttons |
VBAbortRetryIgnore |
2 |
Show abort, retry, ignore buttons |
VBYesNoCancel |
3 |
Show yes, no cancel buttons |
VBYesNo |
4 |
Show yes, no buttons |
VBRetryCancel |
5 |
Show retry, cancel buttons |
VBCritical |
16 |
Show critical message icon |
VBQuestion |
32 |
Show warning query button |
VBExclamation |
48 |
Show warning message icon |
VBInformation |
64 |
Show information message icon |
VBDefaultButton1 |
0 |
First button is default |
VBDefaultButton2 |
256 |
Second button is default |
VBDefaultButton3 |
512 |
Third button is default |
VBDefaultButton4 |
768 |
Fourth button is default |
VBApplicationModal |
0 |
Demands that the user respond to the dialog before allowing continuation of work in current application |
VBSystemModal |
4096 |
Causes suspension of all applications until the user responds to the dialog |
We need to change our code to show a different kind of message box, give the user a choice about shutting the server down, evaluate what they tell us, and act accordingly.
Let's do each of those steps in order. First, I change the message box to display yes, no, and cancel buttons:
' Get the message box MsgBoxVar = MsgBox(MsgTxtVar, VBYesNo, "SQL Server Info")
Hmmm. I don't like the MsgBoxVar variable name anymore, since it's no longer just a display. I'm actually performing an action on the server, and the variable now stores what the user wants to do. So, I change the variable name to reflect that:
' Variables for the text boxes Dim ControlVar Dim MsgTxtVar
And then I change the variable in the message box area as well:
ControlVar = MsgBox(MsgTxtVar, 4, "SQL Server Info")
That's better. Now the ControlVar variable holds the number that represents the button the user clicked. If you change a variable name, it's important to change it everywhere, at the same time. Missing a variable is one of the top coding mistakes!
I need to tell the user that clicking on the Yes button will shut the server down. I put that at the end of the MsgTxt variable:
' Fill the variable with server properties MsgTxtVar = "Name: " & oServer.Name & VbCRLf _ & "ANSI Nulls: " & oServer.AnsiNulls & VbCRLf _ & "Host: " & oServer.HostName & VbCRLf _ & "Service Name (2): " & oServer.ServiceName & VbCRLf _ & "Auto-Start (2): " & oServer.AutoStart & VbCRLf _ & "Version: " & oServer.VersionMajor & "." _ & oServer.VersionMinor & VbCRLf _ & oServer.VersionString & VbCRLf _ & VbCRLf & "Shut Down SQL Server Service?"
Notice that I put one more VbCRLf in there, so that it really sets the text off and makes it more visible.
When the user clicks a button, the number corresponding to that button is now stored in the ControlVar variable. All we have left to do is take the captured value and perform a SQL Server shutdown, if that's what is requested. Here's a chart of possible values from a message box:
VBOK |
1 |
OK |
VBCancel |
2 |
Cancel |
VBAbort |
3 |
Abort |
VBRetry |
4 |
Retry |
VBIgnore |
5 |
Ignore |
VBYes |
6 |
Yes |
VBNo |
7 |
No |
Now I create another "if" block to perform the action:
If ControlVar = VBYes then oServer.Shutdown End If
When the user runs this code, the system generates an error. The reason for this is that you've removed the object that you've been referencing, so VBScript gets a little confused as to what you're talking about. It's kind of like talking to someone that you think is in the room when they've already left.
I'm OK with this error, though, because it's descriptive enough to let the user know that the server is off now. If we wanted to have a more orderly shutdown out of our VBScript program, we'd handle this a bit differently. For now, this works.
Let's take a look at the final code:
' dmoInfoAndShutDown.vbs ' Created: 12/10/04 - Buck Woody ' Change Log: '12/11/04 - Buck Woody - Added comments, InputBox. '12/17/04 - Buck Woody - Changed Server object to 'SQLServer2 and added two new properties to show. Also 'added the ability to shut down the server. ' Variable to hold Server Name Dim ServerNameVar ' Variables for the text boxes Dim ControlVar Dim MsgTxtVar ' Ask for the name ServerNameVar = InputBox("Enter Server Name:") If ServerNameVar = "" Then ServerName = "(local)" End If ' Create the server object using SQL-DMO Set oServer = CreateObject("SQLDMO.SQLServer2") ' Login with current Windows account oServer.LoginSecure = True oServer.Connect ServerNameVar ' Fill the variable with server properties MsgTxtVar = "Name: " & oServer.Name & VbCRLf _ & "ANSI Nulls: " & oServer.AnsiNulls & VbCRLf _ & "Host: " & oServer.HostName & VbCRLf _ & "Service Name (2): " & oServer.ServiceName & VbCRLf _ & "Auto-Start (2): " & oServer.AutoStart & VbCRLf _ & "Version: " & oServer.VersionMajor & "." _ & oServer.VersionMinor & VbCRLf _ & oServer.VersionString & VbCRLf _ & VbCRLf & "Shut Down Server Service?" ' Get the message box ControlVar = MsgBox(MsgTxtVar, VBYesNo, "SQL Server Info") If ControlVar = VBYes then oServer.Shutdown End If ' Clean up Set oServer = Nothing
Notice that I changed the program's filename to reflect what it does. Using more powerful languages such as C#, you could make these functions into separate parts of the program, and call them from a better interface. We'll continue to use VBScript for our examples, and just make each one a separate file.
The same code I'll show you, however, would work inside a Visual Basic program (assuming you give the variables a type and set a reference to the SQL-DMO library).
And here's what the code looks like when it runs:
Next time, we'll explore the database object. See you then!
Online Resources
The full documentation for the Server Object Library can be found here.
If you're anxious to get started with deeper programming, you can find a great site on SQL Development here.
InformIT Tutorials and Sample Chapters
Sharon Dooley discusses SQL-DMO in her book called SQL Server 7 Essential Reference that you can read right here on Safari.