SQL Server Reference Guide

Mar 28, 2003

␡

⎙ Print

< Back Page 48 of 365 Next >

It is vital to understand your system, and in part one of this tutorial I explained how you can find the “Meta-data” or “data about data” — on your system, including the server settings and data structures. In the previous tutorial, I explained the “proper” way to query your system, using the “sp_help” stored procedures, the graphical tools, and several system functions. In this tutorial, I will spend a little more time “under the covers”, and explore the ways you can query system tables to see the state of your server.

I do not recommend that you use the system tables unless you have to. The whole point of those views, stored procedures and functions on the server is so that the data is “abstracted” away for you. That way the system tables can change, but your data will always be available. However, sometimes, especially in the earlier versions of SQL Server, the system tables provided the richest view of all of the system objects. In addition, most of the time those tables have remained stable. So knowing the system objects provides a “lingua franca” of sorts between the versions.

To begin, you need to understand a little about the system databases. You get four databases automatically when you install SQL Server:

master
model
msdb
tempdb

The “master” database is where we will spend the most time in this tutorial. It holds much of the data that SQL Server uses to run itself. I will show you some of the most interesting tables you have there, but there are many others that we will not cover.

The “model” database is used whenever you create a new database. Anything you put in the model database is placed in any other database you create after that. It does not affect restored or attached databases, but serves as a template when you type CREATE DATABASE or use the graphical tools to create a database. Other than the system tables for a database (which I will explain shortly), there are not any system objects we are interested in here.

The “msdb” database is used by the SQL Server Agent system. I will not cover those tables in this tutorial, but I will cover it later. There is a tremendous amount of information you can get from this database regarding maintenance plans, backups, replication, Agent Jobs and more.

The “tempdb” database is created each time the system starts up, and is destroyed each time the system shuts down. I won’t cover anything in this database in this tutorial.

So let’s get started with the tables that show system information, and then move on to the database and security information. Once again, I’ll use SQL Server 2000 for this tutorial, since it is the earliest version I talk about on this site. With only a few exceptions (such as putting sys. in front of the table name) you can still use these queries for SQL Server 2005 and higher. In the next few tutorials I’ll show you

System Information

The primary database you can use for system information is master. Within this database are several tables you can use to get meta-data about the system. The first is sysservers. There are a few settings here that can be useful, but to get a quick list of the SQL Server Instances your system “knows” about, and whether they are local or a linked server, run this query:

SELECT srvname 
, 'ServerType' = CASE isremote 
	WHEN 0 THEN 'LocalServer'
	WHEN 1 THEN 'LinkedServer'
END
FROM sysservers;
GO

Database Information

The master database also stores information about the databases each instance owns. To get a list of databases, you can use the sysdatabases table:

SELECT name AS 'DatabaseName'
, dbid AS 'DatabaseID'
, crdate AS 'CreateDate'
, filename AS 'PrimaryFile'
FROM
sysdatabases
ORDER BY name;
GO

The important field here is dbid, which is the unique key for each database. We will use that to create other interesting information shortly.

For the rest of the database information, you set the context, using the USE databasename; GO query. Each database has a set of system tables used to track information for that database.

The previous query only shows the primary file. Databases have multiple files, for both the data and the logs. Each file has a “logical” name, used by SQL Server, and a “physical” filename that is used by the operating system. To show all of the files for a database, you can query the sysfiles table like this:

SELECT fileid AS 'FileID'
, name AS 'LogicalName'
, 'FileType' = CASE status
	WHEN 1048576 THEN 'DataFile'
	WHEN 1048642 THEN 'LogFile'
END
, filename AS 'FilenName'
, ((size*8192)/1024) AS 'SizeMB' 
FROM sysfiles
ORDER BY LogicalName;
GO

Drilling down to the next level, you can find the database objects using one of the largest tables, called sysobjects. This table will take a few passes, so let’s take a look at a simple query that gets the various objects in a database by type:

SELECT name AS 'ObjectName'
, 'ObjectType' = CASE xtype 
WHEN 'C' THEN 'CHECK'
WHEN 'D' THEN 'DEFAULT'
WHEN 'F' THEN 'FOREIGNKEY'
WHEN 'L' THEN 'Log'
WHEN 'FN' THEN 'ScalarFunction'
WHEN 'IF' THEN 'InlineTableFunction'
WHEN 'P' THEN 'StoredProcedure'
WHEN 'PK' THEN 'PRIMARYKEY'
WHEN 'RF' THEN 'ReplicationFilterStoredProcedure' 
WHEN 'S' THEN 'SystemTable'
WHEN 'TF' THEN 'TableFunction'
WHEN 'TR' THEN 'Trigger'
WHEN 'U' THEN 'UserTable'
WHEN 'UQ' THEN 'UNIQUEConstraint'
WHEN 'V' THEN 'View'
WHEN 'X' THEN 'ExtendedStoredProcedure'
END
FROM sysobjects
ORDER BY xtype, name;
GO

This query is actually kind of cumbersome — it shows all objects in the database. Usually you want a specific object, or a set of objects. For instance, to find all of the stored procedures in a database, you can use this query. Just replace “master” with the name of the database you want to search:

USE master;
GO
SELECT name 
FROM sysobjects
WHERE xtype = 'P'
ORDER BY name;
GO

You’ll notice that when you query the tables (xtype=’U’) you don’t see any columns. Those are actually stored in another table, called syscolumns. Joining the sysobjects table to the syscolumns table, you can find the column names (this makes more sense in a database like pubs):

USE pubs;
GO
SELECT b.name AS 'Table'
, a.name AS 'Column'
FROM syscolumns a
INNER JOIN sysobjects b
ON a.id = b.id
ORDER BY b.name, a.name;
GO

Although you can find the foreign keys and other relationships using system tables, I will cover that in another article.

Security Information

Now we will go after the logins on the server, once again using the master database, this time using the syslogins table. Remember that SQL Server has two principals associated with any particular database object — a server login, and a database user. This query shows the logins for the server:

USE master;
GO

SELECT SID AS 'SecurityID'
, name AS 'UserName' 
, loginname AS 'LoginName'
, 'LoginType' = CASE isntuser
	WHEN 0 THEN 'SQLOrOtherLogin'
	WHEN 1 THEN 'WindowsUserAccount'
END
FROM syslogins
ORDER BY name, loginname;
GO

Just as we moved into the database for specific database information, you will need to change the “context” of the database you are working in by using the pull-down graphical tool in your query tool. Personally, I always use the USE statement, because that works for both the graphical tools and any scripting I do.

Because there are actually two principals involved (the server login and the database user), I like to make sure I know how the two are linked. Normally you’ll create the same name for both accounts, but because we are DBAs, we are naturally untrusting! I always include the name of the server login along with my database users. Here is a query on the sysusers (database) table that shows that information:

USE pubs;
GO

SELECT a.name AS 'DatabaseUser'
, b.loginname AS 'ServerLogin'
FROM sysusers a
INNER JOIN master.dbo.syslogins b
ON a.sid = b.sid 
ORDER BY a.name;
GO

There are other methods that you can use to get meta-data about your systems. In the next tutorial, I will show you the Dynamic Management Views you have for SQL Server 2005 and higher. And in the references section, I will show you how to use the Database Management Objects (DMO) and PowerShell in a programming route to find meta-data. You have many options.

InformIT Articles and Sample Chapters

There is a lot more information on the system tables in the article SQL Building Blocks and Server Settings

Books and eBooks

My good friend Richard Waymire has a rundown on this same kind of information, all the way back in SQL Server version 7, in Sams Teach Yourself Microsoft SQL Server 7 in 21 Days, available in the (free) InformIT Reference Library.

Online Resources

Once you learn these tables, you can read the next tutorial that shows you how to use the newer functions and views for the same info. But Microsoft also has a complete article describing the relationships between the old system tables that I’ve shown here and the newer functions: http://msdn.microsoft.com/en-us/library/ms187997(SQL.90).aspx

And if you want a full download of an Entity Relationship Diagram (ERD) of the system tables in SQL Server 2000, you can get that here for free: http://microsoft.apress.com/asptodayarchive/72995/using-sql-server-system-tables-metadata

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