- 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 database platforms, you set up the environment to allow access to various database objects and server and platform settings, but you don’t have a great deal of control after the rights to those objects and system settings are granted. And in many cases you have to work in a reactive mode, where you monitor for changes and then react to them once they have occurred.
Policy-Based Management, a new feature starting with SQL Server 2008, is a new way of managing your SQL Server systems. Using a series of new settings, you can prescribe the way you want your server settings and database objects to be, and the system will take the responsibility to make things stay that way. In a sense, you’re defining your intent for the system, and the system maintains that intent.
You do all this using various Policies that you can define or import to your system. In this tutorial I’ll explain the parts of this new feature, and I’ll demonstrate a simple Policy that you can follow in the next tutorial.
Policy-Based Management Components
I’ll begin with a definition of all the new terms you’ll need to learn to use Policy-Based Management. These are new terms in some cases and in others it’s a word that has been “re-used.” Understanding these terms is the first thing you need to learn.
I’ll include a rather busy graphic here, but you can refer back to it as you read the following sections. This represents not only the components of Policy-Based Management, but also the flow of the Policy checking and enforcement:
Policy
A SQL Server 2008 “Policy” is the outermost container of all of the rest of the elements. It is actually an XML document, but in a moment I’ll show you how to create the Policy with the graphical tools that you can find in SQL Server Management Studio (SSMS). This document can be stored on the server in the msdb database, or on the file system. By storing them in the database, you provide a central, secure location where you can run them. By storing them on the file system, you can copy them and send them around wherever you like. You can also export a Policy to a file, or import a Policy file into the msdb database.
Microsoft includes several Policies in the initial installation, as files on the hard drive. Many of these are based on the SQL Server “Best Practices Analyze,” or BPA. You can find them here: C:\Program Files\microsoft sql server\100\Tools\Policies.
A Policy also can be enabled or disabled — meaning that you can make a Policy but not have it available to run if you wish.
Target
Each Policy can be applied to one or more databases and database objects. Interestingly, you can “filter” which databases or database objects you want to exclude by using a “Condition” that I’ll explain in a moment.
Facet
A Policy-Based Management “Facet” is one or more database objects, or in fact the database or a server Instance. On each Facet is a set of “Properties” or “Fields.” For instance, one of the Facets is “Database.” On that Facet is a Property called @Name, which is the name of the database.
Now you might think that this is redundant — after all, a Database object already has a “Name” Property that you can read programmatically and with Transact-SQL commands. But Facets go further — they are not only single objects like Databases but other, well, Facets of database objects or even combinations of objects.
Microsoft has included many Facets in SQL Server 2008, and plans to include more in future releases. You can find most of the Facets by right-clicking any database object in SSMS and selecting “Facets” from the menu that appears. Here’s a partial list:
- Application Role
- Asymmetric Key
- Audit
- Backup Device
- Broker Priority
- Broker Service
- Certificate
- Credential
- Cryptographic Provider
- Data File
- Database
- Database Audit Specification
- Database Ddl Trigger
- Database Maintenance
- Database Option
- Database Performance
- Database Role
- Database Security
- Default
- Endpoint
- File Group
- Full Text Catalog
- Full Text Index
- Full Text Stop List
- Index
- Linked Server
- Log File
- Login
- Login Options
- Message Type
- Multipart Name
- Name
- Partition Function
- Partition Scheme
- Plan Guide
- Remote Service Binding
- Resource Governor
- Resource Pool
- Rule
- Schema
- Server
- Server Audit
- Server Audit Specification
- Server Configuration
- Server Ddl Trigger
- Server Information
- Server Performance
- Server Security
- Server Settings
- Server Setup
- Service Contract
- Service Queue
- Service Route
- Statistic
- Stored Procedure
- Surface Area
- Surface Area for AS
- Surface Area for RS
- Symmetric Key
- Synonym
- Table
- Table Options
- Trigger
- User
- User Defined Aggregate
- User Defined Data Type
- User Defined Function
- User Defined Table Type
- User Defined Type
- User Options
- View
- View Options
- Workload Group
- Xml Schema Collection
You can only add one Facet to a Policy at a time, but you can have multiple Policies on a given set of targets.
Condition
Conditions are where the real power comes in for Policy-Based Management. A Condition is one or more comparisons of a Facet property to a value. For instance, one condition you might create could involve the Database Facet and its @LastBackupDate field. You could compare that using an equality (=) or a greater or lesser than, or even an inequality (!=) to a date you select. This particular condition would show if the date that the database was last backed up was equal (or some other comparison) to a specific date. I use this Condition frequently to check that the database has been backed up in today’s date, using a value of “GetDate().”
That brings up an interesting point. You could hard-code a value that you want to compare, and this is what you’ll do quite often — perhaps you’re comparing the @RecoverModel value to “Simple.” But if the value can be checked against a function (like GETDATE()) then you can create a very flexible set of conditions to work with.
You can have multiple conditions against a single Facet. So you could check that a Database Facet is in @RecoveryModel=”Simple” and @LastBackupDate = GetDate(). This lets you set up the exact status you want your databases to be in, and then you can check all your databases at once to match against these settings.
Breaking out the Facets and Conditions like this means that they can be re-used — in fact, the “Targets” I mentioned earlier are just Conditions against Facets. So you could apply the settings you just created against the Database Facet on Targets that are based on only user databases — not system ones.
It’s a bit like a chess game — it’s simple to explain, but as you start combining the possible choices, it can become very complex. I’ll demonstrate a few practical examples in the next tutorial so that this makes a little more sense.
Policy-Based Management Evaluation Modes
Once the Policy is defined against a set of Targets, you’ll notice several “Evaluation Modes” as a selection. I’ll explain each one in turn, and then I’ll show you how they work in the next tutorial.
One Change: Prevent
This mode is only available for SQL Server version 2008 and higher, and only for events that happen within a transaction. Don’t worry — if you can’t run the Policy in this mode, the system will prevent you from choosing it.
What happens during this mode is that when a user or process attempts to complete the action, the Policy-Based Management (PBM) Engine detects the attempt as violating the Policy and then it issues a rollback command. That’s why this mode is available only in SQL Server 2008 Targets — the older versions of SQL Server don’t have this engine.
One Change: log only
This mode is also only available for SQL Server version 2008 and higher. In this case the event is not rolled back, but it is recorded in the SQL Server Error Logs. It’s also recorded in a set of tables in the msdb database, and you’ll get a visual signal on the objects that are “out of Policy.”
On schedule
This mode is also only available for SQL Server version 2008 and higher. With this mode, you set a schedule which will run across all of the servers you designate and check the Policy. If the Policy is violated, it is logged just as in “log only.”
On demand
This mode is available for SQL Server version 2000 and higher. All you do is right-click the Policy and “evaluate” it against the servers you select. The results of the evaluation are once again stored in tables in the msdb database and shown on the screen.
I’ve mentioned PowerShell before here at InformIT, and you can use that to evaluate a Policy as well. In fact, you can schedule a PowerShell script, and you can evaluate a Policy in PowerShell, and you can use the “On demand” mode in a Policy, so using this method you can indeed schedule a Policy against SQL Server 2000 and 2005 systems! I’ll show you how to do that in the next installment as well.
InformIT Articles and Sample Chapters
There’s a lot more about PowerShell starting in this series of updates here in the SQL Server Reference Guide. You can read up on that before you move on to the next tutorial.
Books and eBooks
Ross Mistry has a great book, SQL Server 2005 Management and Administration, that will help you understand the general settings that you can use as Facet choices.
Online Resources
The official documentation for PBM is here.