- 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 my last article, I introduced SQL-DMO, and how you can use VBScript to implement it. In this installment, I expand the small program I created to include more useful features. I also introduce more concepts related to the Server Object.
Let's take a look at the program as it stands now:
Set oServer = CreateObject("SQLDMO.SQLServer") oServer.LoginSecure = True oServer.Connect "(local)" MsgBox oServer.Name Set oServer = Nothing
This is a very simple program: it connects to a SQL Server and displays its name.
One axiom of programming is that your applications should have as much re-use as possible. That means you should think about what you need the program to do, and make it as extensible as possible early in the game.
In this light, one issue with the current code is that it is tied to a single server: (local). To be sure, you can always re-code the server name every time you use the program. However, a better way is to allow the user to enter a server's name when the program starts. To do that, we use a new VBScipt command, called InputBox.
First, let's look at the new code. Then I'll explain the new entries:
' dmo.vbs ' Created: 12/10/04 - Buck Woody ' Change Log: 12/11/04 - Buck Woody - Added ' comments, InputBox. ' Variable to hold Server Name Dim ServerNameVar ' Ask for the name ServerNameVar = InputBox("Enter Server Name:") ' Create the server object using SQL-DMO Set oServer = CreateObject("SQLDMO.SQLServer") ' Login with current Windows account oServer.LoginSecure = True oServer.Connect(ServerNameVar) ' Display Server Name MsgBox oServer.Name ' Clean up Set oServer = Nothing
Whoa! Lots of new code here but not really. Most of the extra verbiage involves the comments I raved about in my earlier articles on programming.
Since I'm keeping this code around, I have to follow my own advice and include comments to make the code more readable and supportable. Comments in VBScript (unlike T-SQL comments) start with a single tick-mark, like this: ' which tells VBScript to ignore all the words on that line.
The next new touch is the addition of a variable to hold the name:
Dim ServerNameVar
The "Dim" part stands for "Dimension," which actually means to set apart some memory. In most programming languages, such as Visual Basic.Net, you would also need to assign a "type" to the variable that is, set the kind of data that the variable can hold, such as "string" (a string of characters), "numeric" (general numbers), and so forth. VBScript doesn't need to be typed; in fact, it doesn't support typing. In any case, you still need to declare a variable like this to use it.
One way to request input from the user is with the InputBox function:
ServerNameVar = InputBox("Enter Server Name:")
With this line, I set the variable I created to the value returned by the InputBox() function. The InputBox() function is really just a call to another program, which creates a Windows message box with a text input area. I passed the text for the question to the function as well; in VBScript, unlike T-SQL, double-quotes enclose text.
Now that I have the name of the server, I can use it in place of the server name that was hard-coded earlier:
oServer.Connect(ServerNameVar)
In effect, this program does the same thing it did earlier, but now it's more extensible.
Let's add some more functionality by learning a little more about the Server object.
As I explained earlier, the SQL-DMO library contains various objects, such as the Server object that we've been using. Objects have properties, which are attributes that you can read and sometimes set. I've used one here already, the .Name property. We can begin to build a more useful program by reading a few more properties for display. Let's add more information to what the message box shows us.
Before we do, take a moment to think about the best way to do that. We could add more properties and formatting to the MsgBox function, but a more efficient way would be to create a variable to hold everything we want and then just use the variable for the text in the MsgBox function. That way, should the information need to change, only the variable has to change, not the code logic.
I'll implement that in the code, along with more properties. Here's the expanded variable area:
Dim ServerNameVar Dim MsgBoxVar Dim MsgTxtVar ...
Notice I've added two variables. The first (MsgBoxVar) holds the return value of the MsgBox() function, just as we did with the InputBox() function earlier. The other variable (MsgTxtVar) holds the object properties I'm after.
Here I fill the MsgTxtVar variable:
' Fill the variable with server properties MsgTxtVar = "Name: " & oServer.Name & VbCRLf _ & "ANSI Nulls: " & oServer.AnsiNulls & VbCRLf _ & "Host: " & oServer.HostName & VbCRLf _ & "Version: " & oServer.VersionMajor & "." _ & oServer.VersionMinor & VbCRLf _ & oServer.VersionString
I added some text (such as "Name: ") and the & symbol. The & symbol joins things together, such as text and variables as we have here. I also added a VBScript constant, called VbCRLf. This constant string is a signal to VBScript to add a carriage-return and line-feed. The _ symbol is used to continue a line, which I had to do in order to show the code properly on the screen. That isn't needed in normal coding, but it can help readability.
You can see that I asked whether the server is set to use ANSI NULLs (.AnsiNulls property), the host name of the server (.HostName property), the version number (.VersionMajor and .VersionMinor properties) and the full version string (.VersionString).
NOTE
Check the references at the end of this article to find even more properties to display. Some of them can be set as well as read, so exercise caution here.
To make this work, the MsgBox function has to take the form MsgBox(text, MsgBox type, title). The text variable is what we've seen before, and the MsgBox type sets the kind of message box I want. The default is a simple box with an OK button (mode 0), but I'll change that to an information box by using mode 64. Finally, I'll give it a title.
Cut-and-paste this code into notepad and run it:
' dmo.vbs ' Created: 12/10/04 - Buck Woody ' Change Log: 12/11/04 - Buck Woody - Added ' comments, InputBox. ' 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.SQLServer") ' 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 _ & "Version: " & oServer.VersionMajor & "." _ & oServer.VersionMinor & VbCRLf _ & oServer.VersionString ' Get the message box MsgBoxVar = MsgBox(MsgTxtVar, 64, "SQL Server Info") ' Clean up Set oServer = Nothing
You may have noticed one other addition. Just after the InputBox() function, I added the following lines:
If ServerNameVar = "" Then ServerName = "(local)" End If
The "If" statement in VBScript tells the program what to do based on a condition. In this case, I got tired of typing "(local)", so the lines above state that if the ServerNameVar contains nothing (that is, if the user presses an ENTER on the first box) represented here as two quotes with nothing in between, then the value would be set to (local). This is called an "If-Then" block. I'll use these fairly often in our programming examples.
So far, the program only returns information about a server to a message box using various properties. In the next installment, I'll show you how to extend the program to read a few more properties and even perform an action on the server object using a method.
Online Resources
The full documentation for the Server Object Library can be found 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.