SQL Server Reference Guide

Mar 28, 2003

␡

⎙ Print

< Back Page 264 of 365 Next >

In this tutorial I’m continuing a series on building a system that you can use to monitor and track your SQL Server systems, and in fact, any kind of system you like (The first article in this series is here). You can use the concepts you find here for lots of SQL Server applications, since in essence it uses many of the features and tools in SQL Server, specifically SQL Server 2008.

At the bottom of this article I reference a CodePlex (Microsoft’s open-source software site) where I’m creating a solution called the SQL Central Management System, or SQLCMS. If you’re interested in participating, just post a notice there that you want to join in the solution. We’ll design it together. I’m working through that project in this series of articles.

In the solution I’m building, there are three basic “components”:

Storage
Execution
Reporting

This tutorial covers one aspect of the execution component of the project, and in specific using this system as a central repository for your performance information.

Using the Management Data Warehouse (MDW) Feature for Performance Collection for SQL Server 2008 Instances

In a previous tutorial, I explained the new Data Collector and Management Data Warehouse feature in SQL Server 2008. The Data Collector is the part that is configured on each of the systems you want to monitor (which is why it is only available for SQL Server 2008) and it uses a series of SQL Server Agent Jobs and SQL Server Integration Services Packages to collect and store data about the performance of the system. It stores this locally in a file on each system, and then at a defined interval it loads that data up into the Management Data Warehouse, which I’m storing on my SQLCMS server.

The process for this, then, is quite straightforward. You simply set up the MDW database (using the Wizards explained in that previous tutorial) and specify the SQLCMS server as the storage unit. You then run the Wizards again on each SQL Server 2008 Instance (with the exception of SQL Server Express Edition, which doesn't have the Agent or SSIS installed) and point those to the SQLCMS server. The only caveat is that you should open each collection_set*_upload SQL Agent Job on these systems and stagger them by a few minutes or so. That way you won’t have everyone uploading their data to the MDW at the same time, and you’ll have a better performing SQLCMS.

You can also opt to collect data from the SQLCMS server as well, and that’s often a good idea. I normally only enable the disk collections, since that’s all I really care about.

I’ve presented various queries to deal with the MDW database in other places, but I’ll consolidate them here with comments to show you what they do. This example will show you the base tables and also a simple example of joining them to get database sizes and so on.

/* 
Title: MDW Queries.sql
Purpose: Holds the MAPS queries if that database is used.
Version: 1.0
Modification History:
04/30/2009 - Buck Woody - Initial Script Creation
Requirements: 
1. SQL Server 2008
2. The Management Data Warehouse feature from SQL Server 2008 to be installed and run once for each instance you wish to monitor.
(Replace the MDW database name if you’re using something else)
Optional: 
*/

USE MDW;
GO

/* Base Information  - More is here: http://msdn.microsoft.com/en-us/library/bb677306.aspx */
SELECT     *
FROM  mdw.sys.schemas;
GO

/* Instances that are tracked */
SELECT     *
FROM mdw.core.source_info_internal
--WHERE instance_name = 'ERP'

/* The snapshots that are tracked against an instance */
SELECT *
FROM mdw.core.snapshots_internal
WHERE source_id = 1;
GO

/* The type of Collectors that the MDW collects */
SELECT * 
FROM  msdb.dbo.syscollector_collector_types ct 
INNER JOIN mdw.core.supported_collector_types_internal ti 
ON ct.collector_type_uid = ti.collector_type_uid;
GO

/* A particular snapshot - this one is the disk information */
SELECT    *
FROM    mdw.snapshots.disk_usage
WHERE  snapshot_id = 1

/* Database Sizes and Growths */
SELECT
    c.instance_name
  , a.dbsize / 102 AS 'DBSizeMB'
  , a.logsize
  , a.ftsize
  , a.database_name
  , a.collection_time
FROM
    MDW.snapshots.disk_usage a INNER JOIN
    MDW.core.snapshots_internal b
    ON a.snapshot_id = b.snapshot_id INNER JOIN
    MDW.core.source_info_internal c
    ON b.source_id = c.source_id
ORDER BY
    c.instance_name
  , a.database_name
  , a.collection_time ASC

You can, of course, report on all kinds of information stored in the MDW database using those base tables at the top of the queries. And you can extend the Data Collectors to get your own counters — but that’s another tutorial.

The key now is to use the links in the Instance names in the MDW to link back to the SQL Server 2008 Central Management Server feature, which I documented in this series. Using those names, you can link up the MDW tables to show the MAPS data I've explained, or any other data that you collect. Because the Instance Name is the only element that is common across all of the features I’m using, I use it as a natural Primary Key — something I rarely do in other applications. It’s not the best practice, but it’s not the end of the world, either. There will only be a relatively small (less than a few thousand) servers that you’ll probably track with this system, so there is a low risk of data corruption due to a natural Primary Key.

Using your own processes for performance collection for SQL Server Instances

Perhaps you don’t want to use the Data Collector for your SQL Server 2008 Instances, or perhaps you still have SQL Server 2005 (or even lower) versions in your organization that you want to monitor.

That’s fine — you can still leverage the MDW feature to help you out with those collections. I recommend that you create the MDW database as a storage location for your data, so that in case you want to put your SQL Server 2008 Instances under Data Collection you can. I also advocate that you turn on the standard Data Collectors for the SQLCMS server (which is a SQL Server 2008 Instance), even if you subsequently disable them. If you do that, you’ll have access to the definitions of the data that they collect.

On my system, I’ve done that very thing. Then, I drilled down in SQL Server Management Studio (SSMS) to the Management node, and then expanded the Data Collection and then System Data Collection Sets node. From there I can see the three Data Collection Sets that were created using the Wizard I followed earlier, just as I described in my previous tutorial on the Management Data Warehouse feature.

Here’s where the payoff comes in. I can see what Microsoft is doing to collect data from SQL Server 2008, and I can use that information to collect it against “lower” versions of SQL Server, in particular SQL Server 2005. It’s like accessing the best minds at Microsoft for performance tuning advice.

Here’s how I do that (by the way, reverse engineering is normally frowned upon, but I checked with the team that owns this feature at Microsoft and they said in this case it’s OK):

I selected the Server Activity Data Collection Set, and then right-clicked it. From the menu that appeared, I selected Properties.

Recall that the Data Collection Sets can be made up of three kinds of actions: SQL Queries, Performance Monitor Counters, and SQL Traces. In this case, I see in the top panel that two of these were used: SQL Queries and Performance Monitor Counters.

I simply click on those items in the top panel, and the results are shown in the bottom panel. Now it’s a matter of copying out the data in the bottom and collecting it into the SQLCMS system into the MDW or other database.

So how do I do that? There are lots of options, from using SSIS to the Performance Monitor in Windows — and that’s something I’ll explore in a future tutorial. Stay tuned!

InformIT Articles and Sample Chapters

If you’re not familiar with the Windows Performance Monitor, you’ll need some background for the next article in this series. Windows 2000 Performance Tools: Leverage Native Tools for Performance Monitoring and Tuning will get you started.

Books and eBooks

You don’t have to use any of this to have a great solution for managing and monitoring not only SQL Server but all kinds of products. Microsoft has a good solution called System Center, and System Center Operations Manager 2007 Unleashed is a great book on it. (Also available as a downloadable eBook and in Safari Books Online.)

Online Resources

The SQL Central Management System (SQLCMS) CodePlex project is located here.

< Back Page 264 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