SQL Server Reference Guide

Mar 28, 2003

␡

⎙ Print

< Back Page 212 of 365 Next >

In part one of this set of articles, I explained that there are several programs you can buy to document and track your server's status and performance. In this article, I show you a few scripts to do the same thing.

This isn't a complete tutorial; in the future I'll show you how to build a database to hold the results of these scripts and the jobs to schedule them. This section should give you an idea of the kinds of information you can get — there's a lot more depth.

To get information about your server and its databases, we rely on three tools: the system tables, system stored procedures, and system functions.

The system tables are located in the master database. This database is the first one started by SQL Server, and it contains all the rest of the information SQL Server needs to start and secure the rest of them. Microsoft has stated that basing information on these tables is risky, as they do not guarantee the contents or structure of these tables during an upgrade or patch. You should never place anything in the master database; you could compromise your whole system if you do.

We also make use of one other database, msdb. This database is used for anything that is scheduled or controlled by the SQL Server Agent. This includes items like jobs, certain DTS packages, and any HTML output jobs.

I've broken these scripts up into parts for a couple of reasons. First, we can spend a little time explaining the methods for each one. Second, some information (such as the server name) is more static, and doesn't need to be gathered as often. Other information (like performance metrics) has a higher granularity and lends itself to more frequent collection. By breaking the script into smaller pieces, you can apply different schedules to the collection.

I normally save the results of these queries into a tracking database. By appending the name of the server to each line of data, I can "roll up" all the data on every server I have to monitor in one central place. I can then run metrics and reports to show performance trends, to project server and storage needs, and so forth.

So now: on with the scripts.

First, we'll get the basic information. We can get the server name (and the instance name) in several ways, but a simple system variable or two suffices:

SELECT @@SERVERNAME
SELECT @@SERVICENAME
GO

If you want to jump ahead a bit, you might need to convert the result if you're going to store it in a table. Here's how to do that:

SELECT CONVERT(VARCHAR(30),@@SERVERNAME)
GO

You can use that trick with any of the system variables I'll show you.

Now on to the version information. You can use another variable for that:

SELECT @@VERSION
GO

What you get back is the version of SQL Server you're running, along with a number. The number represents the service pack you have installed. Microsoft publishes the numbering in each service pack, but here's a quick table:

Version Number	Service Pack
8.00.194	Microsoft SQL Server 2000
8.00.384	Microsoft SQL Server 2000 SP1
8.00.532	Microsoft SQL Server 2000 SP2
8.00.760	Microsoft SQL Server 2000 SP3
8.00.818	Microsoft SQL Server 2000 SP3 w/ Cumulative Patch MS03-031
7.00.623	Microsoft SQL Server 7.0
7.00.699	Microsoft SQL Server 7.0 SP1
7.00.842	Microsoft SQL Server 7.0 SP2
7.00.961	Microsoft SQL Server 7.0 SP3
7.00.1063	Microsoft SQL Server 7.0 SP4
6.50.201	Microsoft SQL Server 6.5 RTM
6.50.213	Microsoft SQL Server 6.5 SP1
6.50.240	Microsoft SQL Server 6.5 SP2
6.50.258	Microsoft SQL Server 6.5 SP3
6.50.281	Microsoft SQL Server 6.5 SP4
6.50.415	Microsoft SQL Server 6.5 SP5
6.50.416	Microsoft SQL Server 6.5 SP5a
6.50.479	Microsoft SQL Server 6.5 SP5a Update

You can construct a rather fancy CASE statement to print out the versions based on the number.

Using the system variables gives you a lot of control over the format of the server, instance name and version, but there's a handy stored procedure that rolls a lot more information up into one set. Here's that stored procedure and the output it created on my system:

EXEC master..xp_msver
GO 
----------------------------------------------------------
Index Name        Internal_Value Character_Value                           
------ -------------------------------- -------------- ----------------------------------1  ProductName      NULL   Microsoft SQL Server
2  ProductVersion     524288   8.00.760
3  Language       1033   English (United States)
4  Platform       NULL   NT INTEL X86
5  Comments       NULL   NT INTEL X86
6  CompanyName      NULL   Microsoft Corporation
7  FileDescription     NULL   SQL Server Windows NT
8  FileVersion      NULL   2000.080.0760.00
9  InternalName      NULL   SQLSERVR
10  LegalCopyright     NULL   © 1988-2003 Microsoft Corp. All rights reserved.
11  LegalTrademarks     NULL   Microsoft® is a registered trademark of Microsoft Corporation. Windows(TM) is a trademark of Microsoft Corporation
12  OriginalFilename     NULL   SQLSERVR.EXE
13  PrivateBuild      NULL   NULL
14  SpecialBuild      49807360  NULL
15  WindowsVersion     170393861  5.1 (2600)
16  ProcessorCount     1    1
17  ProcessorActiveMask    1    00000001
18  ProcessorType     586   PROCESSOR_INTEL_PENTIUM
19  PhysicalMemory     511   511 (536334336)
20  Product ID      NULL   NULL
(20 row(s) affected)

Knowing the version can be very useful if you're trying to diagnose a particular issue that was solved in a service pack.

Now that you know the a bit about the server, we need to make sure the maintenance plans and backups have been running on the databases. There are a few stored procedures and system variables we can look to here as well, and we can also make use of the msdb database. Here's the script for the backups:

SELECT   SUBSTRING(s.name,1,40)AS ’DatabaseName’,
  CAST(b.backup_start_date AS char(11))AS ’LastBackupDate ’,
  CASE WHEN b.backup_start_date > DATEADD(dd,-1,getdate())
    THEN ’Backup is current within a day’
      WHEN b.backup_start_date > DATEADD(dd,-7,getdate())
    THEN ’Backup is current within one week’
    ELSE ’Backup is older than one week’
    END
    AS ’Status’

FROM   master..sysdatabases  s
LEFT OUTER JOIN  msdb..backupset b
  ON s.name = b.database_name
  AND b.backup_start_date = 
    (SELECT MAX(backup_start_date)
    FROM msdb..backupset
    WHERE database_name = b.database_name
    AND type = ’D’)    
WHERE    s.name <> ’tempdb’
ORDER BY   s.name
GO

Notice the CASE statements in this script, which check for the backups in the msdb database and set the status text. I've got a week set here, but you can adjust the granularity by editing the DATEADD lines.

Now you can get the maintenance plan histories:

SELECT   succeeded
  , plan_name
  , database_name
  , activity
  , end_time
  , duration
  , message
FROM msdb..sysdbmaintplan_history
ORDER BY 
  succeeded
GO

This brings back all steps in all plans, ordered by the success bit. You can limit the dates you bring back with the end_time column.

Now that you know whether the backups and maintenance are up to date, you can find out more about the databases. To find out about what databases are on the system, use this script:

EXEC sp_helpdb
GO

With that information, you can find out more about a particular database:

EXEC sp_helpdb ’pubs’ 
GO

Okay, now you've got a good start on our documentation.

There are lots more scripts you can run to find out everything that is going on with the server. Another useful stored procedure can tell you about the users on the system:

EXEC sp_helplogins
GO

Notice that most of these stored procedures started with sp_help. You can find more of these stored procedures in Books Online.

You may have noticed that the stored procedures are easier to use than going after the system variables and other scripts. So why not just use those system stored procedures?

You certainly can, especially if you're using a VB or C# program to present the results. However, if you intend to store the results in a database, you run into a problem. Several of these system stored procedures return more than one "set" of data. This means that a single statement can't fill a table, unless you do some fancy variable work.

So, what if you want the power of the system stored procedures but you want more control so that the return data can be placed in a table? You can use another stored procedure to find the SQL statements that SQL Server is running to produce this output, and then use those statements with the SELECT...INTO clause to fill out the tables in your monitoring database. Here's a sample:

EXEC sp_helptext ’master..sp_helpdb’
GO

If you execute that statement on your system, you'll see the inner workings of the Microsoft stored procedures.

There's a lot more to talk about here — we'll definitely return to the system tables and variables in future articles. The important thing is to build your own arsenal of scripts to document your systems.

Informit Articles and Sample Chapters

Hand-in-hand with database documentation is change control. You'll find a great article about that here.

Online Resources

The system properties I told you about are located here. This is a great resource with lots of information on servers and databases.

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