SQL Server Reference Guide

Mar 28, 2003

␡

⎙ Print

< Back Page 94 of 365 Next >

Policy-Based Management, a new feature starting with SQL Server 2008, is a new way of managing your SQL Server systems. As I explained in Part One of this series, 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 the last tutorial I explained the parts of this new feature, and in this tutorial I’ll demonstrate a simple Policy that you can follow. In the final installment I’ll also show you the Policies that come “out of the box” with SQL Server 2008, where you can store them and run them from, and even how to run them with PowerShell against a server.

As you read through this tutorial, refer back to this primary graphic in Part One. This will help you track where you are in the process of creating a Policy.

Creating a Policy using Policy-Based Management

As I mentioned in the last tutorial, Policy-Based Management (PBM) is a SQL Server 2008 (and higher) feature only. You must create the Policy using SQL Server 2008, but you can run (which is actually called “Evaluating”) the Policy against SQL Server 2000 and 2005 servers, but you have to do that from the SQL Server 2008 system.

If you want to create your own Policy, open up SQL Server Management Studio (SSMS) on your SQL Server 2008 test system and follow along with me on the screens that I show here. I use a Virtual Machine for all my testing, so it stays self-contained and I can practice things like this without affecting any production systems.

Planning the Policy

Before you even get started, you need to plan what you want the Policy to do. You want to put that Policy in terms of the desired state — the way you want the Instance, database or database object to be. You’ll “evaluate” the server against the Policy, and it will tell you if the object is in that state. The one difference, as I mentioned in the last tutorial, is that in some cases you can actually prevent the object from taking that state. In this tutorial, I’ll stick with just reporting the violation of the desired state.

For this example, I’ve decided that none of my databases should be in the “Simple” recovery model. So the Policy statement I’ll work from is pretty simple:

“All databases must not be in the ‘Simple’ recovery model.”

I write them out, just like that. Notice that even though this is a negative condition (“No databases”), the test will be in the positive. What that means is that when the Policy is evaluated, it will only fail when it isn’t in the state I want. That limits what I have to go investigate — the only databases I really care about are the ones that are in “Simple” recovery model. All the others are OK. Keep that in mind as you design your own Policies, and at least for the first few, write them as simple sentences like this.

Creating the Policy

Once I open SSMS, I connect to a server, and then drill down to the Management | Policy Management | Policies node. Even if I want to store the Policy as a file and not in the database, it still has to be created here.

Figure 1

Next, I right-click that node and select “New Policy...” from the menu that appears.

<<Graphic: sqlsrv012309_PBM-2.tif>>

Figure 2

As I’ve mentioned before, whenever you see those three periods after a menu command, it means there are more choices to make. Making that menu selection brings up the first panel I need to fill out for the Policy:

Figure 3

At this stage all I do is name the Policy, and again, I keep that in to the state I want. I’ve got mine pretty specific here — I want to make sure that when if it evaluates to “False”, I know what that means.

Next I click on the “Description” link in the far left-hand part of this pane. That brings up an area where I can enter a more verbose description, which I’ll do. This description is presented to the user (or the developer to pass on to the user), so it needs to be very explanatory.

I can also set a “Category” for the Policy. This isn’t a requirement, but it does help me sort things later, so I add one called “Standards” for this particular example.

The “Text to display” box is presented to the user (or developer) in a separate area when the policy is violated. It’s a lot shorter, so I’ll enter a less verbose message here.

The “Address:” box contains text that also displays when the Policy is violated, but it is sent as a hyperlink. That way the user can click on the link to find out more information, or even open an e-mail to an address of my choice. I can use an HTTP, HTTPS, or MAILTO address as I have here.

Figure 4

With all of that filled out, I switch back to the “General” tab of this pane.

Figure 3

Assigning a Condition

Now it’s time to add the condition I’m checking for. Again, refer back to the graphic from the first tutorial if you need to check where you are. On the “General” tab of this panel, I click the arrow at the end of the “Check Condition” box and either select a condition I’ve made before, or “New condition...” to make a new one. Since I don’t have a condition for this already, I’ll make a new one now.

Figure 5

Once I click that line, I’m placed in a new panel to select a Facet (read that last tutorial for more on that) and the condition I’m looking for. First, I have to name it. I always use the specific item I’m testing here, since I might re-use this condition in another Policy someday. After that, I’ll select the “Database” facet, and then select the @RecoveryModel field. The comparison is “Not” (which is the != part) and the “Value” is “Simple”. It might look a little complicated, but if you read through the last tutorial again it makes sense. I click OK and I’m done.

Figure 6

Setting the Targets, Evaluation Mode and Server Restrictions

All that is left now is to set any targets I want. In this case, I want every database this way, but you might want to modify that to only user databases. If you want to change which databases this Policy will evaluate, then click the “Every” link you see here and you’ll enter the process for yet another condition. As you build your conditions you’ll find that you can use them over and over, which makes the process faster and easier.

I described the Evaluation Modes in the last tutorial, so I won’t cover that again here. I’ll set this one to “On demand”, which means I’ll run it manually whenever I want.

Finally, you can restrict the Policy to servers that meet your criteria using — once again — another condition. This condition, however, is limited to server facets.

Figure 7

I click OK, and the Policy is ready to run. At this point it is saved in the database of the server where I created it. Later I’ll explain how you can save it out to a file and run it from there.

Evaluating (or Running) a Policy

Just inside the “Policies” node, I right-click the name of the Policy I just created and then select “Evaluate” from the menu that appears. If you don’t see the screen the way I have it here, just press F7 on your keyboard.

Figure 8

Since I’m choosing to run the Policy from this node, it will run against this server. Once it runs, I see that I have some databases that fail the condition:

Figure 9

Clicking on the “View” link in the “Details” area at the bottom part of the panel shows me the parts of the condition that failed. That really isn’t necessary here since this is a simple condition — the Recover Model — but in a complex situation it matters which part of the condition fails.

In the next tutorial I’ll show you how to run the Policy from a file, against a remote server or servers, and how to run it from PowerShell.

InformIT Articles and Sample Chapters

There’s a lot more about PowerShell starting in this series of updates in this 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 on administration, Microsoft SQL Server 2005 Management and Administration, which will help you understand the general settings that you can use as Facet choices.

Online Resources

The official documentation for PBM is here.

< Back Page 94 of 365 Next >

🔖 Save To Your Account

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.

Privacy Notice

Overview

Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information

To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.

Surveys

Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.

Newsletters

If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information

Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.

Security

Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.

Children

This site is not directed to children under the age of 13.

Marketing

Pearson may send or direct marketing communications to users, provided that

Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
Such marketing is consistent with applicable law and Pearson's legal obligations.
Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information

If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.

Choice/Opt-out

Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information

Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents

California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure

Pearson may disclose personal information, as follows:

As required by law.
With the consent of the individual (or their parent, if the individual is a minor)
In response to a subpoena, court order or legal process, to the extent permitted or required by law
To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
To investigate or address actual or suspected fraud or other illegal activities
To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.

Links

This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact

Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice

We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020

Email Address