Home > Articles > Data > SQL Server

📄 Contents

  1. SQL Server Reference Guide
  2. Introduction
  3. SQL Server Reference Guide Overview
  4. Table of Contents
  5. Microsoft SQL Server Defined
  6. SQL Server Editions
  7. SQL Server Access
  8. Informit Articles and Sample Chapters
  9. Online Resources
  10. Microsoft SQL Server Features
  11. SQL Server Books Online
  12. Clustering Services
  13. Data Transformation Services (DTS) Overview
  14. Replication Services
  15. Database Mirroring
  16. Natural Language Processing (NLP)
  17. Analysis Services
  18. Microsot SQL Server Reporting Services
  19. XML Overview
  20. Notification Services for the DBA
  21. Full-Text Search
  22. SQL Server 2005 - Service Broker
  23. Using SQL Server as a Web Service
  24. SQL Server Encryption Options Overview
  25. SQL Server 2008 Overview
  26. SQL Server 2008 R2 Overview
  27. SQL Azure
  28. The Utility Control Point and Data Application Component, Part 1
  29. The Utility Control Point and Data Application Component, Part 2
  30. Microsoft SQL Server Administration
  31. The DBA Survival Guide: The 10 Minute SQL Server Overview
  32. Preparing (or Tuning) a Windows System for SQL Server, Part 1
  33. Preparing (or Tuning) a Windows System for SQL Server, Part 2
  34. Installing SQL Server
  35. Upgrading SQL Server
  36. SQL Server 2000 Management Tools
  37. SQL Server 2005 Management Tools
  38. SQL Server 2008 Management Tools
  39. SQL Azure Tools
  40. Automating Tasks with SQL Server Agent
  41. Run Operating System Commands in SQL Agent using PowerShell
  42. Automating Tasks Without SQL Server Agent
  43. Storage – SQL Server I/O
  44. Service Packs, Hotfixes and Cumulative Upgrades
  45. Tracking SQL Server Information with Error and Event Logs
  46. Change Management
  47. SQL Server Metadata, Part One
  48. SQL Server Meta-Data, Part Two
  49. Monitoring - SQL Server 2005 Dynamic Views and Functions
  50. Monitoring - Performance Monitor
  51. Unattended Performance Monitoring for SQL Server
  52. Monitoring - User-Defined Performance Counters
  53. Monitoring: SQL Server Activity Monitor
  54. SQL Server Instances
  55. DBCC Commands
  56. SQL Server and Mail
  57. Database Maintenance Checklist
  58. The Maintenance Wizard: SQL Server 2000 and Earlier
  59. The Maintenance Wizard: SQL Server 2005 (SP2) and Later
  60. The Web Assistant Wizard
  61. Creating Web Pages from SQL Server
  62. SQL Server Security
  63. Securing the SQL Server Platform, Part 1
  64. Securing the SQL Server Platform, Part 2
  65. SQL Server Security: Users and other Principals
  66. SQL Server Security – Roles
  67. SQL Server Security: Objects (Securables)
  68. Security: Using the Command Line
  69. SQL Server Security - Encrypting Connections
  70. SQL Server Security: Encrypting Data
  71. SQL Server Security Audit
  72. High Availability - SQL Server Clustering
  73. SQL Server Configuration, Part 1
  74. SQL Server Configuration, Part 2
  75. Database Configuration Options
  76. 32- vs 64-bit Computing for SQL Server
  77. SQL Server and Memory
  78. Performance Tuning: Introduction to Indexes
  79. Statistical Indexes
  80. Backup and Recovery
  81. Backup and Recovery Examples, Part One
  82. Backup and Recovery Examples, Part Two: Transferring Databases to Another System (Even Without Backups)
  83. SQL Profiler - Reverse Engineering An Application
  84. SQL Trace
  85. SQL Server Alerts
  86. Files and Filegroups
  87. Partitioning
  88. Full-Text Indexes
  89. Read-Only Data
  90. SQL Server Locks
  91. Monitoring Locking and Deadlocking
  92. Controlling Locks in SQL Server
  93. SQL Server Policy-Based Management, Part One
  94. SQL Server Policy-Based Management, Part Two
  95. SQL Server Policy-Based Management, Part Three
  96. Microsoft SQL Server Programming
  97. An Outline for Development
  98. Database
  99. Database Services
  100. Database Objects: Databases
  101. Database Objects: Tables
  102. Database Objects: Table Relationships
  103. Database Objects: Keys
  104. Database Objects: Constraints
  105. Database Objects: Data Types
  106. Database Objects: Views
  107. Database Objects: Stored Procedures
  108. Database Objects: Indexes
  109. Database Objects: User Defined Functions
  110. Database Objects: Triggers
  111. Database Design: Requirements, Entities, and Attributes
  112. Business Process Model Notation (BPMN) and the Data Professional
  113. Business Questions for Database Design, Part One
  114. Business Questions for Database Design, Part Two
  115. Database Design: Finalizing Requirements and Defining Relationships
  116. Database Design: Creating an Entity Relationship Diagram
  117. Database Design: The Logical ERD
  118. Database Design: Adjusting The Model
  119. Database Design: Normalizing the Model
  120. Creating The Physical Model
  121. Database Design: Changing Attributes to Columns
  122. Database Design: Creating The Physical Database
  123. Database Design Example: Curriculum Vitae
  124. NULLs
  125. The SQL Server Sample Databases
  126. The SQL Server Sample Databases: pubs
  127. The SQL Server Sample Databases: NorthWind
  128. The SQL Server Sample Databases: AdventureWorks
  129. The SQL Server Sample Databases: Adventureworks Derivatives
  130. UniversalDB: The Demo and Testing Database, Part 1
  131. UniversalDB: The Demo and Testing Database, Part 2
  132. UniversalDB: The Demo and Testing Database, Part 3
  133. UniversalDB: The Demo and Testing Database, Part 4
  134. Getting Started with Transact-SQL
  135. Transact-SQL: Data Definition Language (DDL) Basics
  136. Transact-SQL: Limiting Results
  137. Transact-SQL: More Operators
  138. Transact-SQL: Ordering and Aggregating Data
  139. Transact-SQL: Subqueries
  140. Transact-SQL: Joins
  141. Transact-SQL: Complex Joins - Building a View with Multiple JOINs
  142. Transact-SQL: Inserts, Updates, and Deletes
  143. An Introduction to the CLR in SQL Server 2005
  144. Design Elements Part 1: Programming Flow Overview, Code Format and Commenting your Code
  145. Design Elements Part 2: Controlling SQL's Scope
  146. Design Elements Part 3: Error Handling
  147. Design Elements Part 4: Variables
  148. Design Elements Part 5: Where Does The Code Live?
  149. Design Elements Part 6: Math Operators and Functions
  150. Design Elements Part 7: Statistical Functions
  151. Design Elements Part 8: Summarization Statistical Algorithms
  152. Design Elements Part 9:Representing Data with Statistical Algorithms
  153. Design Elements Part 10: Interpreting the Data—Regression
  154. Design Elements Part 11: String Manipulation
  155. Design Elements Part 12: Loops
  156. Design Elements Part 13: Recursion
  157. Design Elements Part 14: Arrays
  158. Design Elements Part 15: Event-Driven Programming Vs. Scheduled Processes
  159. Design Elements Part 16: Event-Driven Programming
  160. Design Elements Part 17: Program Flow
  161. Forming Queries Part 1: Design
  162. Forming Queries Part 2: Query Basics
  163. Forming Queries Part 3: Query Optimization
  164. Forming Queries Part 4: SET Options
  165. Forming Queries Part 5: Table Optimization Hints
  166. Using SQL Server Templates
  167. Transact-SQL Unit Testing
  168. Index Tuning Wizard
  169. Unicode and SQL Server
  170. SQL Server Development Tools
  171. The SQL Server Transact-SQL Debugger
  172. The Transact-SQL Debugger, Part 2
  173. Basic Troubleshooting for Transact-SQL Code
  174. An Introduction to Spatial Data in SQL Server 2008
  175. Performance Tuning
  176. Performance Tuning SQL Server: Tools and Processes
  177. Performance Tuning SQL Server: Tools Overview
  178. Creating a Performance Tuning Audit - Defining Components
  179. Creating a Performance Tuning Audit - Evaluation Part One
  180. Creating a Performance Tuning Audit - Evaluation Part Two
  181. Creating a Performance Tuning Audit - Interpretation
  182. Creating a Performance Tuning Audit - Developing an Action Plan
  183. Understanding SQL Server Query Plans
  184. Performance Tuning: Implementing Indexes
  185. Performance Monitoring Tools: Windows 2008 (and Higher) Server Utilities, Part 1
  186. Performance Monitoring Tools: Windows 2008 (and Higher) Server Utilities, Part 2
  187. Performance Monitoring Tools: Windows System Monitor
  188. Performance Monitoring Tools: Logging with System Monitor
  189. Performance Monitoring Tools: User Defined Counters
  190. General Transact-SQL (T-SQL) Performance Tuning, Part 1
  191. General Transact-SQL (T-SQL) Performance Tuning, Part 2
  192. General Transact-SQL (T-SQL) Performance Tuning, Part 3
  193. Performance Monitoring Tools: An Introduction to SQL Profiler
  194. Performance Tuning: Introduction to Indexes
  195. Performance Monitoring Tools: SQL Server 2000 Index Tuning Wizard
  196. Performance Monitoring Tools: SQL Server 2005 Database Tuning Advisor
  197. Performance Monitoring Tools: SQL Server Management Studio Reports
  198. Performance Monitoring Tools: SQL Server 2008 Activity Monitor
  199. The SQL Server 2008 Management Data Warehouse and Data Collector
  200. Performance Monitoring Tools: Evaluating Wait States with PowerShell and Excel
  201. Practical Applications
  202. Choosing the Back End
  203. The DBA's Toolbox, Part 1
  204. The DBA's Toolbox, Part 2
  205. Scripting Solutions for SQL Server
  206. Building a SQL Server Lab
  207. Using Graphics Files with SQL Server
  208. Enterprise Resource Planning
  209. Customer Relationship Management (CRM)
  210. Building a Reporting Data Server
  211. Building a Database Documenter, Part 1
  212. Building a Database Documenter, Part 2
  213. Data Management Objects
  214. Data Management Objects: The Server Object
  215. Data Management Objects: Server Object Methods
  216. Data Management Objects: Collections and the Database Object
  217. Data Management Objects: Database Information
  218. Data Management Objects: Database Control
  219. Data Management Objects: Database Maintenance
  220. Data Management Objects: Logging the Process
  221. Data Management Objects: Running SQL Statements
  222. Data Management Objects: Multiple Row Returns
  223. Data Management Objects: Other Database Objects
  224. Data Management Objects: Security
  225. Data Management Objects: Scripting
  226. Powershell and SQL Server - Overview
  227. PowerShell and SQL Server - Objects and Providers
  228. Powershell and SQL Server - A Script Framework
  229. Powershell and SQL Server - Logging the Process
  230. Powershell and SQL Server - Reading a Control File
  231. Powershell and SQL Server - SQL Server Access
  232. Powershell and SQL Server - Web Pages from a SQL Query
  233. Powershell and SQL Server - Scrubbing the Event Logs
  234. SQL Server 2008 PowerShell Provider
  235. SQL Server I/O: Importing and Exporting Data
  236. SQL Server I/O: XML in Database Terms
  237. SQL Server I/O: Creating XML Output
  238. SQL Server I/O: Reading XML Documents
  239. SQL Server I/O: Using XML Control Mechanisms
  240. SQL Server I/O: Creating Hierarchies
  241. SQL Server I/O: Using HTTP with SQL Server XML
  242. SQL Server I/O: Using HTTP with SQL Server XML Templates
  243. SQL Server I/O: Remote Queries
  244. SQL Server I/O: Working with Text Files
  245. Using Microsoft SQL Server on Handheld Devices
  246. Front-Ends 101: Microsoft Access
  247. Comparing Two SQL Server Databases
  248. English Query - Part 1
  249. English Query - Part 2
  250. English Query - Part 3
  251. English Query - Part 4
  252. English Query - Part 5
  253. RSS Feeds from SQL Server
  254. Using SQL Server Agent to Monitor Backups
  255. Reporting Services - Creating a Maintenance Report
  256. SQL Server Chargeback Strategies, Part 1
  257. SQL Server Chargeback Strategies, Part 2
  258. SQL Server Replication Example
  259. Creating a Master Agent and Alert Server
  260. The SQL Server Central Management System: Definition
  261. The SQL Server Central Management System: Base Tables
  262. The SQL Server Central Management System: Execution of Server Information (Part 1)
  263. The SQL Server Central Management System: Execution of Server Information (Part 2)
  264. The SQL Server Central Management System: Collecting Performance Metrics
  265. The SQL Server Central Management System: Centralizing Agent Jobs, Events and Scripts
  266. The SQL Server Central Management System: Reporting the Data and Project Summary
  267. Time Tracking for SQL Server Operations
  268. Migrating Departmental Data Stores to SQL Server
  269. Migrating Departmental Data Stores to SQL Server: Model the System
  270. Migrating Departmental Data Stores to SQL Server: Model the System, Continued
  271. Migrating Departmental Data Stores to SQL Server: Decide on the Destination
  272. Migrating Departmental Data Stores to SQL Server: Design the ETL
  273. Migrating Departmental Data Stores to SQL Server: Design the ETL, Continued
  274. Migrating Departmental Data Stores to SQL Server: Attach the Front End, Test, and Monitor
  275. Tracking SQL Server Timed Events, Part 1
  276. Tracking SQL Server Timed Events, Part 2
  277. Patterns and Practices for the Data Professional
  278. Managing Vendor Databases
  279. Consolidation Options
  280. Connecting to a SQL Azure Database from Microsoft Access
  281. SharePoint 2007 and SQL Server, Part One
  282. SharePoint 2007 and SQL Server, Part Two
  283. SharePoint 2007 and SQL Server, Part Three
  284. Querying Multiple Data Sources from a Single Location (Distributed Queries)
  285. Importing and Exporting Data for SQL Azure
  286. Working on Distributed Teams
  287. Professional Development
  288. Becoming a DBA
  289. Certification
  290. DBA Levels
  291. Becoming a Data Professional
  292. SQL Server Professional Development Plan, Part 1
  293. SQL Server Professional Development Plan, Part 2
  294. SQL Server Professional Development Plan, Part 3
  295. Evaluating Technical Options
  296. System Sizing
  297. Creating a Disaster Recovery Plan
  298. Anatomy of a Disaster (Response Plan)
  299. Database Troubleshooting
  300. Conducting an Effective Code Review
  301. Developing an Exit Strategy
  302. Data Retention Strategy
  303. Keeping Your DBA/Developer Job in Troubled Times
  304. The SQL Server Runbook
  305. Creating and Maintaining a SQL Server Configuration History, Part 1
  306. Creating and Maintaining a SQL Server Configuration History, Part 2
  307. Creating an Application Profile, Part 1
  308. Creating an Application Profile, Part 2
  309. How to Attend a Technical Conference
  310. Tips for Maximizing Your IT Budget This Year
  311. The Importance of Blue-Sky Planning
  312. Application Architecture Assessments
  313. Transact-SQL Code Reviews, Part One
  314. Transact-SQL Code Reviews, Part Two
  315. Cloud Computing (Distributed Computing) Paradigms
  316. NoSQL for the SQL Server Professional, Part One
  317. NoSQL for the SQL Server Professional, Part Two
  318. Object-Role Modeling (ORM) for the Database Professional
  319. Business Intelligence
  320. BI Explained
  321. Developing a Data Dictionary
  322. BI Security
  323. Gathering BI Requirements
  324. Source System Extracts and Transforms
  325. ETL Mechanisms
  326. Business Intelligence Landscapes
  327. Business Intelligence Layouts and the Build or Buy Decision
  328. A Single Version of the Truth
  329. The Operational Data Store (ODS)
  330. Data Marts – Combining and Transforming Data
  331. Designing Data Elements
  332. The Enterprise Data Warehouse — Aggregations and the Star Schema
  333. On-Line Analytical Processing (OLAP)
  334. Data Mining
  335. Key Performance Indicators
  336. BI Presentation - Client Tools
  337. BI Presentation - Portals
  338. Implementing ETL - Introduction to SQL Server 2005 Integration Services
  339. Building a Business Intelligence Solution, Part 1
  340. Building a Business Intelligence Solution, Part 2
  341. Building a Business Intelligence Solution, Part 3
  342. Tips and Troubleshooting
  343. SQL Server and Microsoft Excel Integration
  344. Tips for the SQL Server Tools: SQL Server 2000
  345. Tips for the SQL Server Tools – SQL Server 2005
  346. Transaction Log Troubles
  347. SQL Server Connection Problems
  348. Orphaned Database Users
  349. Additional Resources
  350. Tools and Downloads
  351. Utilities (Free)
  352. Tool Review (Free): DBDesignerFork
  353. Aqua Data Studio
  354. Microsoft SQL Server Best Practices Analyzer
  355. Utilities (Cost)
  356. Quest Software's TOAD for SQL Server
  357. Quest Software's Spotlight on SQL Server
  358. SQL Server on Microsoft's Virtual PC
  359. Red Gate SQL Bundle
  360. Microsoft's Visio for Database Folks
  361. Quest Capacity Manager
  362. SQL Server Help
  363. Visual Studio Team Edition for Database Professionals
  364. Microsoft Assessment and Planning Solution Accelerator
  365. Aggregating Server Data from the MAPS Tool

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 ). 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”:

  1. Storage
  2. Execution
  3. Reporting

This tutorial covers the storage aspect of the project, and in specific the tables (what I’ll call “Base Tables”) that I’ve created in my sample project. And that brings up a note I’ll post in every one of the articles in this series:

OK, with that out of the way, we can get started.

Recall that I mentioned some requirements for the SQLCMS solution, and at least three of them are important for the storage aspect of the system. The SQLCMS needs to use standard “components,” be extensible, and be based on components that can be switched in or out. At the very base level of the project, we need a place to store the results of the survey of the system, some performance and growth metrics, and anything else we want to record and report on. We could use XML files, text files, Microsoft Access Databases, Microsoft Excel Spreadsheets, or any number of other products to store the data – all would store data.

But remember that I am building my solution on several new features in SQL Server 2008 that are specifically designed to assist with multiple-server management, so it only makes sense to store the results of my system polling in a SQL Server 2008 database. It meets all the requirements of the system, and it makes querying the data across all of the features seamless. It also scales well, is well supported, and of course as DBA’s and administrators, we know the features we can use to leverage the data.

But that isn’t the end of the story. Even after deciding to use a SQL Server 2008 database as the storage for the solution, there are at least three ways to do that.

Use Current Databases and Tables from Other Sources

As I mentioned in the previous article, there are software packages out there that already perform much of the work you need done in a management and/or monitoring solution. Perhaps you’re reading this tutorial because you want to see how you can “fold in” the tools, processes and features in SQL Server 2008 to one of those solutions to shore up what they may not do, or at least do well.

If so, then they may already have a database, perhaps even on SQL Server 2008, where the discovery and other data has been stored. You could, and possibly should, leverage that data. But before you do…

Not every software license allows you to access the databases underneath them. The structure might change, and the vendor probably hasn’t explained to you how they insert, update or delete the data they track. And even if it were technically possible to find out where the data they have is stored, or how it is updated, it might not be legal to do so. You’ll need to read and understand their license terms, and perhaps even speak with their sales staff to make sure you have written permission to access the data without using their software.

If that isn’t possible, then you might consider at least exporting the data they’ve collected so that you don’t have to perform the discovery or collection methods yourself. Even there, you need to check that license to make sure that you’re allowed to do that. You don’t want to get into trouble with a vendor because you leveraged their data without permission.

Another possibility is to create a view in your own database that references the base tables in the application’s database. That way you only store the data once, and you have the control to make the views with the column names the way you want, with the security the way you want. You could also use a remote query, linked server or other methods to leave the data in the other platform but show it in the database where you’re tracking other information.

Create Completely New Tables in a Separate Database

Let’s assume you’ve either exported the data you want (legally), or you are going to collect it yourself and go it alone. If that’s the case, you might want to investigate creating your own database in SQL Server 2008 yourself.

If you do, I recommend that you follow the steps in the next option. It’s the solution I chose, and its advantage is that you can use the same techniques whether you’re using a completely new database or one that already exists.

In any case, make sure you treat this database like you would any production database. Remember, this data is production for you. And if you begin to depend on it, which I’m sure you will, it needs to be safe, secure, and performant, just like any other database. It will need a maintenance plan, security groups and so on.

While we’re on that subject, this system has to be on a licensed copy of SQL Server 2008. You can certainly experiment with an an evaluation edition or the Developer edition, but you'll need at least Standard edition to legally use it in production. You'll only need as many client licenses as DBA's, of course, so it isn't an expensive proposition.

Personally I'm using Enterprise edition, with just a few CALs (Client Licenses) rather than a CPU license. That keeps the cost down, but gives me compression, which becomes really important when I start storing a lot of performance data. More on that later.

Adding Tables and Objects to a Current Database

The solution I settled on is to use a database that already exists in SQL Server 2008 — sort of. I’ve explained the Management Data Warehouse feature in another tutorial, and I mentioned there that when you run the Wizard to use the feature for the first time, it creates a new database. I named mine “MDW.” Although this is a Microsoft “owned” database, they have publicly stated that they do not mind if you create other objects in it. There are three schemas that Microsoft creates within the database: core, snapshots, and optionally custom_snapshots. We’ve been told that as long as we stay away from those three schemas, we can create objects in that database.

Why use this database? My choice was guided by a few factors. Number one, the MDW database stores performance and other useful data. Also, this is the database that is used by the Enterprise Policy Management Framework, something I’ll cover in future articles on this topic.

So if you are following along with this example, make sure you read that article on the MDW system and run the Wizard to create the database.

Even if you don’t use the MDW database and decide to create your own, you can follow along with the rest of this tutorial.

The SQLCMS Schemas

Since I’m using the MDW database, I need to create some new schemas to hold my database objects. Even if you’re using your own database, it’s a best practice to ensure that you create your objects in schemas as well, so this works for you as well. If you’re new to schemas, it’s actually a pretty simple concept. They are simply “containers” for other objects, so that you can group them together.

A tip that I’ll show and use throughout this process is to self-document my objects. In other words, I’ll make sure that even if you don’t have this document, you could figure out (probably) what I’m doing with each object. This is a tip that I use on just about everything, and it involves “Extended Properties.” You can get to the Extended Properties by right-clicking an object in SQL Server Management Studio, and looking at the last tab for that object. You can then add an extended property, which involves a “tag” or name of the description, and then the data you want to add to the object. From then on, you can query the Extended Properties of the object. I use that feature to add documentation to my objects, so that I know what they are and are used for.

You can also do this with a stored procure, called sys.sp_addextendedproperty. You’ll see this in the code in a moment.

First, which schemas do we need? Well, in my solution, I wanted to make sure I captured the pertinent data, but leave it open to have more information if I wanted to extend it later. Since I’m tracking data about SQL Server Instances, I’ll certainly need a schema for that. Here’s the code I used to create that schema, once I set the database context to the MDW database:

-- Change MDW to the database of your choice
USE MDW;
GO 
CREATE SCHEMA [sqlinstances] ;
GO
Now to annotate it to explain what it does:
EXEC sys.sp_addextendedproperty @name=N'MS_Description'
, @value=N'Stores Information specific to SQL Server Instances.' 
, @level0type=N'SCHEMA'
,@level0name=N'sqlinstances';
GO

Now, whenever anyone wants to see the annotations I’ve put on the objects, they can use the system function called fn_listexendedproperty to see them. Here’s the query that shows schema information, once again making sure I’m in the MDW database first:

-- New schemas and their tables
SELECT  *
FROM    fn_listextendedproperty(NULL
, 'schema'
, DEFAULT
, DEFAULT
, DEFAULT
, DEFAULT
, DEFAULT) ;
GO

I’ll show those again when we’re done with the process.

Since SQL Server runs on a Windows Server, I decided to create a schema for that as well. True, I could store that information in the SQL Server schema, but by separating them this way I can allow system administrators to leverage this system as well, or even Microsoft Exchange, System Center, SharePoint or any other kind of platform to leverage the server data as well. Here’s the code for that — a little more verbose, a little more proper to create and annotate the schema for the servers:

IF NOT EXISTS (SELECT * FROM sys.schemas WHERE name = N'servers')
EXEC sys.sp_executesql N'CREATE SCHEMA [servers] AUTHORIZATION [dbo]'
GO
IF NOT EXISTS (SELECT * FROM ::fn_listextendedproperty(N'MS_Description' , N'SCHEMA',N'servers', NULL,NULL, NULL,NULL))
EXEC sys.sp_addextendedproperty @name=N'MS_Description', @value=N'Stores data about the Windows or other Servers hosting a platform such 
as SQL Server.' , @level0type=N'SCHEMA',@level0name=N'servers'
GO 

Now on to the tables. I’ll start with the server tables this time. This is the part where your solution may differ from mine — I’ve decided on some base columns that I plan to create, and as long as I know I have these columns, I can add to them later if I need to.

My first table covers some basic information about the server. I toyed with leveraging the data in the MAPS tool, because it is really useful. If you would like to do that, just create views here that reference that data. You can find more about that in this tutorial. More about using the data it stores is here.

Following standard design processes, I’ll only store the data here that is recorded once for each server — to a point. Instead of documenting each one of the columns in this tutorial, open a connection to a SQL Server and try the following queries in a test database to check out the “self documenting” idea:

SET ANSI_NULLS ON
GO

SET QUOTED_IDENTIFIER ON
GO

SET ANSI_PADDING ON
GO

IF NOT EXISTS(SELECT  *
              FROM    sys.objects
              WHERE   object_id = OBJECT_ID(N'[servers].[system]')
                      AND TYPE IN(N'U'))
   BEGIN
         CREATE TABLE [servers].[system]
              (
               [systemKey] [INT] IDENTITY(1,1) NOT NULL
               , [DomainName] [VARCHAR](150) NOT NULL
               , [ServerName] [VARCHAR](150) NOT NULL
               , [NetworkAddress] [VARCHAR](50) NULL
               , [Architecture] [VARCHAR](50) NULL
               , [ProcessorType] [VARCHAR](50) NULL
               , [NumberOfProcessors] [NUMERIC](18,0) NULL
               , [TotalMemoryInstalledMB] [NUMERIC](18,0) NULL
               , [OperatingSystem] [VARCHAR](100) NULL
               , [OperatingServicePack] [VARCHAR](50) NULL
               , [IsClustered] [BIT] NULL
               , [Owner] [VARCHAR](150) NULL
               , [Notes] [VARCHAR](255) NULL
               , [AssetNumber] [VARCHAR](150) NULL
               , [LastUpdated] [DATETIME] NULL
               , CONSTRAINT [PK_system] PRIMARY KEY CLUSTERED([systemKey] ASC) WITH(PAD_INDEX = OFF
               , STATISTICS_NORECOMPUTE = OFF
               , IGNORE_DUP_KEY = OFF
               , ALLOW_ROW_LOCKS = ON
               , ALLOW_PAGE_LOCKS = ON) ON [PRIMARY]
              )
         ON  [PRIMARY]
   END
GO

SET ANSI_PADDING OFF
GO

IF NOT EXISTS(SELECT  *
              FROM    ::fn_listextendedproperty(N'MS_Description', N'SCHEMA', N'servers', N'TABLE', N'system', N'COLUMN', N'systemKey'))
   EXEC sys.sp_addextendedproperty @name = N'MS_Description', @value = N'Primary Key for this Table', 
@level0type = N'SCHEMA', @level0name = N'servers', @level1type = N'TABLE', @level1name = N'system', @level2type = N'COLUMN', @level2name = N'systemKey'
GO

IF NOT EXISTS(SELECT  *
              FROM    ::fn_listextendedproperty(N'MS_Description', N'SCHEMA', N'servers', N'TABLE', N'system', N'COLUMN', N'DomainName'))
   EXEC sys.sp_addextendedproperty @name = N'MS_Description', @value = N'Name of the domain the computer belongs to. Use the ServerName if 
no domain. Makes this row unique.', @level0type = N'SCHEMA', @level0name = N'servers', @level1type = N'TABLE', @level1name = N'system', 
@level2type = N'COLUMN', @level2name = N'DomainName'
GO

IF NOT EXISTS(SELECT  *
              FROM    ::fn_listextendedproperty(N'MS_Description', N'SCHEMA', N'servers', N'TABLE', N'system', N'COLUMN', N'ServerName'))
   EXEC sys.sp_addextendedproperty @name = N'MS_Description', @value = N'HostName of the computer.', @level0type = N'SCHEMA', 
@level0name = N'servers', @level1type = N'TABLE', @level1name = N'system', @level2type = N'COLUMN', @level2name = N'ServerName'
GO

IF NOT EXISTS(SELECT  *
              FROM    ::fn_listextendedproperty(N'MS_Description', N'SCHEMA', N'servers', N'TABLE', N'system', N'COLUMN', N'NetworkAddress'))
   EXEC sys.sp_addextendedproperty @name = N'MS_Description', @value = N'Network address of the server.', @level0type = N'SCHEMA', 
@level0name = N'servers', @level1type = N'TABLE', @level1name = N'system', @level2type = N'COLUMN', @level2name = N'NetworkAddress'
GO

IF NOT EXISTS(SELECT  *
              FROM    ::fn_listextendedproperty(N'MS_Description', N'SCHEMA', N'servers', N'TABLE', N'system', N'COLUMN', N'Architecture'))
   EXEC sys.sp_addextendedproperty @name = N'MS_Description', @value = N'Bit-depth of the motherboard (32, 64, etc).', @level0type = 
N'SCHEMA', @level0name = N'servers', @level1type = N'TABLE', @level1name = N'system', @level2type = N'COLUMN', @level2name = N'Architecture'
GO

IF NOT EXISTS(SELECT  *
              FROM    ::fn_listextendedproperty(N'MS_Description', N'SCHEMA', N'servers', N'TABLE', N'system', N'COLUMN', N'ProcessorType'))
   EXEC sys.sp_addextendedproperty @name = N'MS_Description', @value = N'Vendor and chip name of the central processor(s).', @level0type = 
N'SCHEMA', @level0name = N'servers', @level1type = N'TABLE', @level1name = N'system', @level2type = N'COLUMN', @level2name = 
N'ProcessorType'
GO

IF NOT EXISTS(SELECT  *
              FROM    ::fn_listextendedproperty(N'MS_Description', N'SCHEMA', N'servers', N'TABLE', N'system', N'COLUMN', N'NumberOfProcessors'))
   EXEC sys.sp_addextendedproperty @name = N'MS_Description', @value = N'Number of physical Processors installed.', @level0type = 
N'SCHEMA', @level0name = N'servers', @level1type = N'TABLE', @level1name = N'system', @level2type = N'COLUMN', @level2name = 
N'NumberOfProcessors'
GO

IF NOT EXISTS(SELECT  *
              FROM    ::fn_listextendedproperty(N'MS_Description', N'SCHEMA', N'servers', N'TABLE', N'system', N'COLUMN', N'TotalMemoryInstalledMB'))
   EXEC sys.sp_addextendedproperty @name = N'MS_Description', @value = N'Total amount (in megabytes) of physical memory installed in the 
server.', @level0type =  N'SCHEMA', @level0name = N'servers', @level1type = N'TABLE', @level1name = N'system', @level2type = N'COLUMN', 
@level2name = N'TotalMemoryInstalledMB'
GO

IF NOT EXISTS(SELECT  *
              FROM    ::fn_listextendedproperty(N'MS_Description', N'SCHEMA', N'servers', N'TABLE', N'system', N'COLUMN', N'OperatingSystem'))
   EXEC sys.sp_addextendedproperty @name = N'MS_Description', @value = N'Vendor and SKU name of the operating system installed on the 
server.', @level0type = N'SCHEMA', @level0name = N'servers', @level1type = N'TABLE', @level1name = N'system', @level2type = N'COLUMN', 
@level2name = N'OperatingSystem'
GO

IF NOT EXISTS(SELECT  *
              FROM    ::fn_listextendedproperty(N'MS_Description', N'SCHEMA', N'servers', N'TABLE', N'system', N'COLUMN', N'OperatingServicePack'))
   EXEC sys.sp_addextendedproperty @name = N'MS_Description', @value = N'Service Pack Description of the installed operating system.', 
@level0type = N'SCHEMA', @level0name = N'servers', @level1type = N'TABLE', @level1name = N'system', @level2type = N'COLUMN', 
@level2name = N'OperatingServicePack'
GO

IF NOT EXISTS(SELECT  *
              FROM    ::fn_listextendedproperty(N'MS_Description', N'SCHEMA', N'servers', N'TABLE', N'system', N'COLUMN', N'IsClustered'))
   EXEC sys.sp_addextendedproperty @name = N'MS_Description', @value = N'Specifies whether the operating system is clustered (1) or not (0).', 
@level0type = N'SCHEMA', @level0name = N'servers', @level1type = N'TABLE', @level1name = N'system', @level2type = N'COLUMN', 
@level2name = N'IsClustered'
GO

IF NOT EXISTS(SELECT  *
              FROM    ::fn_listextendedproperty(N'MS_Description', N'SCHEMA', N'servers', N'TABLE', N'system', N'COLUMN', N'Owner'))
   EXEC sys.sp_addextendedproperty @name = N'MS_Description', @value = N'Responsible party for this system. Optional. ', @level0type = N'SCHEMA', @level0name = N'servers', @level1type = N'TABLE', @level1name = N'system', @level2type = N'COLUMN', @level2name = N'Owner'
GO

IF NOT EXISTS(SELECT  *
              FROM    ::fn_listextendedproperty(N'MS_Description', N'SCHEMA', N'servers', N'TABLE', N'system', N'COLUMN', N'Notes'))
   EXEC sys.sp_addextendedproperty @name = N'MS_Description', @value = N'Short set of notes regarding this hardware. Optional.', @level0type = 
N'SCHEMA', @level0name = N'servers', @level1type = N'TABLE', @level1name = N'system', @level2type = N'COLUMN', @level2name = N'Notes'
GO

IF NOT EXISTS(SELECT  *
              FROM    ::fn_listextendedproperty(N'MS_Description', N'SCHEMA', N'servers', N'TABLE', N'system', N'COLUMN', N'AssetNumber'))
   EXEC sys.sp_addextendedproperty @name = N'MS_Description', @value = N'Organization''s asset numbering system identification number. 
Optional.', @level0type = N'SCHEMA', @level0name = N'servers', @level1type = N'TABLE', @level1name = N'system', @level2type = N'COLUMN',
@level2name = N'AssetNumber'
GO

IF NOT EXISTS(SELECT  *
              FROM    ::fn_listextendedproperty(N'MS_Description', N'SCHEMA', N'servers', N'TABLE', N'system', N'COLUMN', N'LastUpdated'))
   EXEC sys.sp_addextendedproperty @name = N'MS_Description', @value = N'The last time this system''s data was updated. Default is insert time.', 
@level0type = N'SCHEMA', @level0name = N'servers', @level1type = N'TABLE', @level1name = N'system', @level2type = N'COLUMN', 
@level2name = N'LastUpdated'
GO

IF NOT EXISTS(SELECT  *
              FROM    ::fn_listextendedproperty(N'Description', N'SCHEMA', N'servers', N'TABLE', N'system', NULL, NULL))
   EXEC sys.sp_addextendedproperty @name = N'Description', @value = N'Systems to track. Could be physical or virtual, but must be a discrete 
computing server.', @level0type = N'SCHEMA', @level0name = N'servers', @level1type = N'TABLE', @level1name = N'system'
GO

IF NOT EXISTS(SELECT  *
              FROM    dbo.sysobjects
              WHERE   id = OBJECT_ID(N'[DF_Table_1_Clustered]')
                      AND TYPE = 'D')
   BEGIN
         ALTER TABLE [servers].[system]
         ADD CONSTRAINT [DF_Table_1_Clustered] DEFAULT((0)) FOR [IsClustered]
   END

GO

IF NOT EXISTS(SELECT  *
              FROM    dbo.sysobjects
              WHERE   id = OBJECT_ID(N'[DF_system_LastUpdated]')
                      AND TYPE = 'D')
   BEGIN
         ALTER TABLE [servers].[system]
         ADD CONSTRAINT [DF_system_LastUpdated] DEFAULT(getdate()) FOR [LastUpdated]
   END

GO

Now, run this query to see what you just created:

SELECT  *
FROM    fn_listextendedproperty(NULL
, 'schema'
, 'servers'
, 'table'
, DEFAULT, NULL, NULL) ;
GO

-- Columns
SELECT 'servers.system' AS 'Table'
      , objname AS 'Column'
      , VALUE AS 'Description'
FROM   fn_listextendedproperty(NULL
, 'schema'
, 'servers'
, 'table'
, 'system'
, 'column'
, DEFAULT) ;
GO

Don’t agree with my choices or layout? Change it! That’s the point of this exercise – it’s your system, and you can change the schemas, layout or anything else in any way you like.

OK, now on to some other information in the server schema. Although the server itself is recorded once, there is other data that I am interested in, specifically the disk information. So I’ll create a “disk” table to hold that.

Here’s where the design becomes a bit more...interesting. Because I’ve chosen to use the MDW database and the Enterprise Policy Management Framework (which will also put some tables in the MDW database) as well as some tables in the msdb database for the Central Management Server (CMS) feature, I’ll have to link everything up with the server name. Normally you want to use a Primary Key to link things together, and normally that is a number or some other value that has nothing to do with the meaning of the data. But since several of the features I’m leveraging are using the server and Instance name as a link, I’ll have to do that as well if I want to remain consistent with them.

I’m OK with this. I’ll never have more than a few dozen servers to contend with, and the data is certainly re-discoverable — it’s not like the server will ever “lose” its name. It might change, but I can handle that as well.

It’s these type of decisions that really make the project yours. Feel free to architect yours differently. Here is the script (and the descriptions again) for the “disk” table:

/* Create the disk table */
SET ANSI_NULLS ON
GO

SET QUOTED_IDENTIFIER ON
GO

SET ANSI_PADDING ON
GO

IF NOT EXISTS(SELECT  *
              FROM    sys.objects
              WHERE   object_id = OBJECT_ID(N'[servers].[disk]')
                      AND TYPE IN(N'U'))
   BEGIN
         CREATE TABLE [servers].[disk]
              (
               [diskKey] [INT] IDENTITY(1,1) NOT NULL
               , [ServerName] [VARBINARY](150) NOT NULL
               , [DriveReference] [VARCHAR](100) NULL
               , [TotalSizeMB] [NUMERIC](18,0) NULL
               , [CurrentlyUsedMB] [NUMERIC](18,0) NULL
               , [Notes] [VARCHAR](255) NULL
               , [LastUpdated] [DATETIME] NULL
               , CONSTRAINT [PK_disk] PRIMARY KEY CLUSTERED([diskKey] ASC) WITH(PAD_INDEX = OFF
               , STATISTICS_NORECOMPUTE = OFF
               , IGNORE_DUP_KEY = OFF
               , ALLOW_ROW_LOCKS = ON
               , ALLOW_PAGE_LOCKS = ON) ON [PRIMARY]
              )
         ON  [PRIMARY]
   END
GO

SET ANSI_PADDING OFF
GO

IF NOT EXISTS(SELECT  *
              FROM    ::fn_listextendedproperty(N'MS_Description', N'SCHEMA', N'servers', N'TABLE', N'disk', N'COLUMN', N'diskKey'))
   EXEC sys.sp_addextendedproperty @name = N'MS_Description', @value = N'Key for the disk table.', @level0type = N'SCHEMA', @level0name = 
N'servers', @level1type = N'TABLE', @level1name = N'disk', @level2type = N'COLUMN', @level2name = N'diskKey'
GO

IF NOT EXISTS(SELECT  *
              FROM    ::fn_listextendedproperty(N'MS_Description', N'SCHEMA', N'servers', N'TABLE', N'disk', N'COLUMN', N'ServerName'))
   EXEC sys.sp_addextendedproperty @name = N'MS_Description', @value = N'Physical or virtual server where this drive is installed. Will be 
denormalized.', @level0type = N'SCHEMA', @level0name = N'servers', @level1type = N'TABLE', @level1name = N'disk', @level2type = N'COLUMN', 
@level2name = N'ServerName'
GO

IF NOT EXISTS(SELECT  *
              FROM    ::fn_listextendedproperty(N'MS_Description', N'SCHEMA', N'servers', N'TABLE', N'disk', N'COLUMN', N'DriveReference'))
   EXEC sys.sp_addextendedproperty @name = N'MS_Description', @value = N'Drive letter, mount point or share location that you want to track for 
this server.', @level0type = N'SCHEMA', @level0name = N'servers', @level1type = N'TABLE', @level1name = N'disk', @level2type = N'COLUMN', 
@level2name = N'DriveReference'
GO

IF NOT EXISTS(SELECT  *
              FROM    ::fn_listextendedproperty(N'MS_Description', N'SCHEMA', N'servers', N'TABLE', N'disk', N'COLUMN', N'TotalSizeMB'))
   EXEC sys.sp_addextendedproperty @name = N'MS_Description', @value = N'Complete size of the drive, in megabytes.', @level0type = 
N'SCHEMA', @level0name = N'servers', @level1type = N'TABLE', @level1name = N'disk', @level2type = N'COLUMN', @level2name =
N'TotalSizeMB'
GO

IF NOT EXISTS(SELECT  *
              FROM    ::fn_listextendedproperty(N'MS_Description', N'SCHEMA', N'servers', N'TABLE', N'disk', N'COLUMN', N'CurrentlyUsedMB'))
   EXEC sys.sp_addextendedproperty @name = N'MS_Description', @value = N'The amount of space left as of this poll.', @level0type = N'SCHEMA', 
@level0name = N'servers', @level1type = N'TABLE', @level1name = N'disk', @level2type = N'COLUMN', @level2name = N'CurrentlyUsedMB'
GO

IF NOT EXISTS(SELECT  *
              FROM    ::fn_listextendedproperty(N'MS_Description', N'SCHEMA', N'servers', N'TABLE', N'disk', N'COLUMN', N'Notes'))
   EXEC sys.sp_addextendedproperty @name = N'MS_Description', @value = N'Short notes about this drive.', @level0type = N'SCHEMA', 
@level0name = N'servers', @level1type = N'TABLE', @level1name = N'disk', @level2type = N'COLUMN', @level2name = N'Notes'
GO

IF NOT EXISTS(SELECT  *
              FROM    ::fn_listextendedproperty(N'MS_Description', N'SCHEMA', N'servers', N'TABLE', N'disk', N'COLUMN', N'LastUpdated'))
   EXEC sys.sp_addextendedproperty @name = N'MS_Description', @value = N'The last time this data was updated. Default is insert date.', 
@level0type = N'SCHEMA', @level0name = N'servers', @level1type = N'TABLE', @level1name = N'disk', @level2type = N'COLUMN', @level2name 
= N'LastUpdated'
GO

IF NOT EXISTS(SELECT  *
              FROM    ::fn_listextendedproperty(N'Description', N'SCHEMA', N'servers', N'TABLE', N'disk', NULL, NULL))
   EXEC sys.sp_addextendedproperty @name = N'Description', @value = N'Stores logical disk information for a server. Links to servers.system 
through ServerName.', @level0type = N'SCHEMA', @level0name = N'servers', @level1type = N'TABLE', @level1name = N'disk'
GO

IF NOT EXISTS(SELECT  *
              FROM    dbo.sysobjects
              WHERE   id = OBJECT_ID(N'[DF_disk_LastUpdated]')
                      AND TYPE = 'D')
   BEGIN
         ALTER TABLE [servers].[disk]
         ADD CONSTRAINT [DF_disk_LastUpdated] DEFAULT(getdate()) FOR [LastUpdated]
   END

GO
/* Show the documentation */
SELECT 'servers.disk' AS 'Table'
      , objname AS 'Column'
      , VALUE AS 'Description'
FROM   fn_listextendedproperty(NULL
, 'schema'
, 'servers'
, 'table'
, 'disk'
, 'column'
, DEFAULT) ;
GO

You can see the kind of data I intend to collect about the disks. Now on to the tables for the SQL Server Instances. I’ll show the code for two tables at one time, one for the Instance itself and the other for the databases on the Instance (remember, we’re still in the MDW database — that’s where this code should run):

SET ANSI_NULLS ON
GO

SET QUOTED_IDENTIFIER ON
GO

SET ANSI_PADDING ON
GO

IF NOT EXISTS(SELECT  *
              FROM    sys.objects
              WHERE   object_id = OBJECT_ID(N'[sqlinstances].[sqlserver]')
                      AND TYPE IN(N'U'))
   BEGIN
         CREATE TABLE [sqlinstances].[sqlserver]
              (
               [sqlserverKey] [INT] IDENTITY(1,1) NOT NULL
               , [ServerName] [VARCHAR](150) NOT NULL
               , [instance_name] [VARCHAR](150) NOT NULL
               , [InstanceMajorVersion] [VARCHAR](50) NULL
               , [InstanceMinorVersion] [VARCHAR](100) NULL
               , [Edition] [VARCHAR](50) NULL
               , [ProcessorsAssigned] [NUMERIC](18,0) NULL
               , [MaxMemoryAssigned] [NUMERIC](18,0) NULL
               , [ClusterNode] [VARCHAR](50) NULL
               , [InstanceStatusFlag] [BIT] NULL
               , [InstanceStatusDescription] [VARCHAR](255) NULL
               , [InstanceOwner] [VARCHAR](150) NULL
               , [InstanceNotes] [VARCHAR](255) NULL
               , [LastUpdated] [DATETIME] NULL
               , CONSTRAINT [PK_sqlserver] PRIMARY KEY CLUSTERED([sqlserverKey] ASC) WITH(PAD_INDEX = OFF
               , STATISTICS_NORECOMPUTE = OFF
               , IGNORE_DUP_KEY = OFF
               , ALLOW_ROW_LOCKS = ON
               , ALLOW_PAGE_LOCKS = ON) ON [PRIMARY]
              )
         ON  [PRIMARY]
   END
GO

SET ANSI_PADDING OFF
GO

IF NOT EXISTS(SELECT  *
              FROM    ::fn_listextendedproperty(N'MS_Description', N'SCHEMA', N'sqlinstances', N'TABLE', N'sqlserver', N'COLUMN', N'sqlserverKey'))
   EXEC sys.sp_addextendedproperty @name = N'MS_Description', @value = N'Primary key for the sqlserver table.', @level0type = N'SCHEMA', 
@level0name = N'sqlinstances', @level1type = N'TABLE', @level1name = N'sqlserver', @level2type = N'COLUMN', @level2name = N'sqlserverKey'
GO

IF NOT EXISTS(SELECT  *
              FROM    ::fn_listextendedproperty(N'MS_Description', N'SCHEMA', N'sqlinstances', N'TABLE', N'sqlserver', N'COLUMN', N'ServerName'))
   EXEC sys.sp_addextendedproperty @name = N'MS_Description', @value = N'Name of the physical or virtual server where this instance is installed. 
Used as a link to other tables in the MDW database.', @level0type = N'SCHEMA', @level0name = N'sqlinstances', @level1type = N'TABLE', 
@level1name = N'sqlserver', @level2type = N'COLUMN', @level2name = N'ServerName'
GO

IF NOT EXISTS(SELECT  *
              FROM    ::fn_listextendedproperty(N'MS_Description', N'SCHEMA', N'sqlinstances', N'TABLE', N'sqlserver', N'COLUMN', N'instance_name'))
   EXEC sys.sp_addextendedproperty @name = N'MS_Description', @value = N'Instance name. Use the server name if this is the DEFAULT instance 
to link properly to other schemas in the MDW database.', @level0type = N'SCHEMA', @level0name = N'sqlinstances', @level1type = N'TABLE', 
@level1name = N'sqlserver', @level2type = N'COLUMN', @level2name = N'instance_name'
GO

IF NOT EXISTS(SELECT  *
              FROM    ::fn_listextendedproperty(N'MS_Description', N'SCHEMA', N'sqlinstances', N'TABLE', N'sqlserver', N'COLUMN', 
N'InstanceMajorVersion'))
   EXEC sys.sp_addextendedproperty @name = N'MS_Description', @value = N'Version of SQL Server installed on this instance.', @level0type = 
N'SCHEMA', @level0name = N'sqlinstances', @level1type = N'TABLE', @level1name = N'sqlserver', @level2type = N'COLUMN', @level2name = 
N'InstanceMajorVersion'
GO

IF NOT EXISTS(SELECT  *
              FROM    ::fn_listextendedproperty(N'MS_Description', N'SCHEMA', N'sqlinstances', N'TABLE', N'sqlserver', N'COLUMN', 
N'InstanceMinorVersion'))
   EXEC sys.sp_addextendedproperty @name = N'MS_Description', @value = N'Service Pack, Hotfix, and / or Cumulative Update installed on this 
instance.', @level0type = N'SCHEMA', @level0name = N'sqlinstances', @level1type = N'TABLE', @level1name = N'sqlserver', @level2type = 
N'COLUMN', @level2name = N'InstanceMinorVersion'
GO

IF NOT EXISTS(SELECT  *
              FROM    ::fn_listextendedproperty(N'MS_Description', N'SCHEMA', N'sqlinstances', N'TABLE', N'sqlserver', N'COLUMN', N'Edition'))
   EXEC sys.sp_addextendedproperty @name = N'MS_Description', @value = N'Edition of SQL Server installed.', @level0type = N'SCHEMA', 
@level0name = N'sqlinstances', @level1type = N'TABLE', @level1name = N'sqlserver', @level2type = N'COLUMN', @level2name = N'Edition'
GO

IF NOT EXISTS(SELECT  *
              FROM    ::fn_listextendedproperty(N'MS_Description', N'SCHEMA', N'sqlinstances', N'TABLE', N'sqlserver', N'COLUMN', 
N'ProcessorsAssigned'))
   EXEC sys.sp_addextendedproperty @name = N'MS_Description', @value = N'Total number of processors assigned to this instance of SQL Server.', 
@level0type = N'SCHEMA', @level0name = N'sqlinstances', @level1type = N'TABLE', @level1name = N'sqlserver', @level2type = N'COLUMN', 
@level2name = N'ProcessorsAssigned'
GO

IF NOT EXISTS(SELECT  *
              FROM    ::fn_listextendedproperty(N'MS_Description', N'SCHEMA', N'sqlinstances', N'TABLE', N'sqlserver', N'COLUMN', 
N'MaxMemoryAssigned'))
   EXEC sys.sp_addextendedproperty @name = N'MS_Description', @value = N'Maximum amount of RAM assigned to this instance.', @level0type = 
N'SCHEMA', @level0name = N'sqlinstances', @level1type = N'TABLE', @level1name = N'sqlserver', @level2type = N'COLUMN', @level2name = 
N'MaxMemoryAssigned'
GO

IF NOT EXISTS(SELECT  *
              FROM    ::fn_listextendedproperty(N'MS_Description', N'SCHEMA', N'sqlinstances', N'TABLE', N'sqlserver', N'COLUMN', N'ClusterNode'))
   EXEC sys.sp_addextendedproperty @name = N'MS_Description', @value = N'If part of a cluster, the name of this node.', @level0type = 
N'SCHEMA', @level0name = N'sqlinstances', @level1type = N'TABLE', @level1name = N'sqlserver', @level2type = N'COLUMN', @level2name = 
N'ClusterNode'
GO

IF NOT EXISTS(SELECT  *
              FROM    ::fn_listextendedproperty(N'MS_Description', N'SCHEMA', N'sqlinstances', N'TABLE', N'sqlserver', N'COLUMN', 
N'InstanceStatusFlag'))
   EXEC sys.sp_addextendedproperty @name = N'MS_Description', @value = N'Shows whether this instance needs attention (1) or not (0).', 
@level0type = N'SCHEMA', @level0name = N'sqlinstances', @level1type = N'TABLE', @level1name = N'sqlserver', @level2type = N'COLUMN', 
@level2name = N'InstanceStatusFlag'
GO

IF NOT EXISTS(SELECT  *
              FROM    ::fn_listextendedproperty(N'MS_Description', N'SCHEMA', N'sqlinstances', N'TABLE', N'sqlserver', N'COLUMN', 
N'InstanceStatusDescription'))
   EXEC sys.sp_addextendedproperty @name = N'MS_Description', @value = N'Description of why this system needs attention.', @level0type = 
N'SCHEMA', @level0name = N'sqlinstances', @level1type = N'TABLE', @level1name = N'sqlserver', @level2type = N'COLUMN', @level2name = 
N'InstanceStatusDescription'
GO

IF NOT EXISTS(SELECT  *
              FROM    ::fn_listextendedproperty(N'MS_Description', N'SCHEMA', N'sqlinstances', N'TABLE', N'sqlserver', N'COLUMN', N'InstanceOwner'))
   EXEC sys.sp_addextendedproperty @name = N'MS_Description', @value = N'Individual or group responsible for this server. Can be used to show 
the on-call person and number.', @level0type = N'SCHEMA', @level0name = N'sqlinstances', @level1type = N'TABLE', @level1name = N'sqlserver', 
@level2type = N'COLUMN', @level2name = N'InstanceOwner'
GO

IF NOT EXISTS(SELECT  *
              FROM    ::fn_listextendedproperty(N'MS_Description', N'SCHEMA', N'sqlinstances', N'TABLE', N'sqlserver', N'COLUMN', N'InstanceNotes'))
   EXEC sys.sp_addextendedproperty @name = N'MS_Description', @value = N'Short notes about this instance.', @level0type = N'SCHEMA', 
@level0name = N'sqlinstances', @level1type = N'TABLE', @level1name = N'sqlserver', @level2type = N'COLUMN', @level2name = N'InstanceNotes'
GO

IF NOT EXISTS(SELECT  *
              FROM    ::fn_listextendedproperty(N'MS_Description', N'SCHEMA', N'sqlinstances', N'TABLE', N'sqlserver', N'COLUMN', N'LastUpdated'))
   EXEC sys.sp_addextendedproperty @name = N'MS_Description', @value = N'Last time this information was gathered. Default is the row insert 
date.', @level0type = N'SCHEMA', @level0name = N'sqlinstances', @level1type = N'TABLE', @level1name = N'sqlserver', @level2type = 
N'COLUMN', @level2name = N'LastUpdated'
GO

IF NOT EXISTS(SELECT  *
              FROM    ::fn_listextendedproperty(N'Description', N'SCHEMA', N'sqlinstances', N'TABLE', N'sqlserver', NULL, NULL))
   EXEC sys.sp_addextendedproperty @name = N'Description', @value = N'SQL Server Instance Information.', @level0type = N'SCHEMA', 
@level0name = N'sqlinstances', @level1type = N'TABLE', @level1name = N'sqlserver'
GO

USE <SourceDatabaseName, varchar(100), MDW>
GO

/* Now the databases */
SET ANSI_NULLS ON
GO

SET QUOTED_IDENTIFIER ON
GO

SET ANSI_PADDING ON
GO

IF NOT EXISTS(SELECT  *
              FROM    sys.objects
              WHERE   object_id = OBJECT_ID(N'[sqlinstances].[database]')
                      AND TYPE IN(N'U'))
   BEGIN
         CREATE TABLE [sqlinstances].[database]
              (
               [databaseKey] [INT] IDENTITY(1,1) NOT NULL
               , [ServerName] [VARCHAR](150) NULL
               , [instance_name] [VARCHAR](150) NULL
               , [DatabaseName] [VARCHAR](100) NULL
               , [LastDatabaseBackup] [DATETIME] NULL
               , [LastLogBackup] [DATETIME] NULL
               , [CurrentDataSizeMB] [NUMERIC](18,0) NULL
               , [CurrentLogSizeMD] [NUMERIC](18,0) NULL
               , [RecoveryModel] [VARCHAR](50) NULL
               , [Notes] [VARCHAR](255) NULL
               , [Purpose] [VARCHAR](255) NULL
               , [LastUpdated] [DATETIME] NULL
               , CONSTRAINT [PK_database] PRIMARY KEY CLUSTERED([databaseKey] ASC) WITH(PAD_INDEX = OFF
               , STATISTICS_NORECOMPUTE = OFF
               , IGNORE_DUP_KEY = OFF
               , ALLOW_ROW_LOCKS = ON
               , ALLOW_PAGE_LOCKS = ON) ON [PRIMARY]
              )
         ON  [PRIMARY]
   END
GO

SET ANSI_PADDING OFF
GO

IF NOT EXISTS(SELECT  *
              FROM    ::fn_listextendedproperty(N'MS_Description', N'SCHEMA', N'sqlinstances', N'TABLE', N'database', N'COLUMN', N'databaseKey'))
   EXEC sys.sp_addextendedproperty @name = N'MS_Description', @value = N'Primary key for database table.', @level0type = N'SCHEMA', 
@level0name = N'sqlinstances', @level1type = N'TABLE', @level1name = N'database', @level2type = N'COLUMN', @level2name = N'databaseKey'
GO

IF NOT EXISTS(SELECT  *
              FROM    ::fn_listextendedproperty(N'MS_Description', N'SCHEMA', N'sqlinstances', N'TABLE', N'database', N'COLUMN', N'ServerName'))
   EXEC sys.sp_addextendedproperty @name = N'MS_Description', @value = N'Partial link to other tables. Also use instance_name to make this 
unique.', @level0type = N'SCHEMA', @level0name = N'sqlinstances', @level1type = N'TABLE', @level1name = N'database', @level2type = 
N'COLUMN', @level2name = N'ServerName'
GO

IF NOT EXISTS(SELECT  *
              FROM    ::fn_listextendedproperty(N'MS_Description', N'SCHEMA', N'sqlinstances', N'TABLE', N'database', N'COLUMN', N'instance_name'))
   EXEC sys.sp_addextendedproperty @name = N'MS_Description', @value = N'Partial link to server. Also use ServerName.', @level0type = 
N'SCHEMA', @level0name = N'sqlinstances', @level1type = N'TABLE', @level1name = N'database', @level2type = N'COLUMN', @level2name = 
N'instance_name'
GO

IF NOT EXISTS(SELECT  *
              FROM    ::fn_listextendedproperty(N'MS_Description', N'SCHEMA', N'sqlinstances', N'TABLE', N'database', N'COLUMN', N'DatabaseName'))
   EXEC sys.sp_addextendedproperty @name = N'MS_Description', @value = N'Name of the database.', @level0type = N'SCHEMA', @level0name = 
N'sqlinstances', @level1type = N'TABLE', @level1name = N'database', @level2type = N'COLUMN', @level2name = N'DatabaseName'
GO

IF NOT EXISTS(SELECT  *
              FROM    ::fn_listextendedproperty(N'MS_Description', N'SCHEMA', N'sqlinstances', N'TABLE', N'database', N'COLUMN', 
N'LastDatabaseBackup'))
   EXEC sys.sp_addextendedproperty @name = N'MS_Description', @value = N'Date and time of the last backup of the database.', @level0type = 
N'SCHEMA', @level0name = N'sqlinstances', @level1type = N'TABLE', @level1name = N'database', @level2type = N'COLUMN', @level2name = 
N'LastDatabaseBackup'
GO

IF NOT EXISTS(SELECT  *
              FROM    ::fn_listextendedproperty(N'MS_Description', N'SCHEMA', N'sqlinstances', N'TABLE', N'database', N'COLUMN', N'LastLogBackup'))
   EXEC sys.sp_addextendedproperty @name = N'MS_Description', @value = N'Date and time of the last log backup.', @level0type = N'SCHEMA', 
@level0name = N'sqlinstances', @level1type = N'TABLE', @level1name = N'database', @level2type = N'COLUMN', @level2name = 
N'LastLogBackup'
GO

IF NOT EXISTS(SELECT  *
              FROM    ::fn_listextendedproperty(N'MS_Description', N'SCHEMA', N'sqlinstances', N'TABLE', N'database', N'COLUMN', 
N'CurrentDataSizeMB'))
   EXEC sys.sp_addextendedproperty @name = N'MS_Description', @value = N'Size of the database as of this poll.', @level0type = N'SCHEMA', 
@level0name = N'sqlinstances', @level1type = N'TABLE', @level1name = N'database', @level2type = N'COLUMN', @level2name = 
N'CurrentDataSizeMB'
GO

IF NOT EXISTS(SELECT  *
              FROM    ::fn_listextendedproperty(N'MS_Description', N'SCHEMA', N'sqlinstances', N'TABLE', N'database', N'COLUMN', 
N'CurrentLogSizeMD'))
   EXEC sys.sp_addextendedproperty @name = N'MS_Description', @value = N'Current log size as of this poll.', @level0type = N'SCHEMA', 
@level0name = N'sqlinstances', @level1type = N'TABLE', @level1name = N'database', @level2type = N'COLUMN', @level2name = 
N'CurrentLogSizeMD'
GO

IF NOT EXISTS(SELECT  *
              FROM    ::fn_listextendedproperty(N'MS_Description', N'SCHEMA', N'sqlinstances', N'TABLE', N'database', N'COLUMN', N'RecoveryModel'))
   EXEC sys.sp_addextendedproperty @name = N'MS_Description', @value = N'Recovery model for the database.', @level0type = N'SCHEMA', 
@level0name = N'sqlinstances', @level1type = N'TABLE', @level1name = N'database', @level2type = N'COLUMN', @level2name = 
N'RecoveryModel'
GO

IF NOT EXISTS(SELECT  *
              FROM    ::fn_listextendedproperty(N'MS_Description', N'SCHEMA', N'sqlinstances', N'TABLE', N'database', N'COLUMN', N'Notes'))
   EXEC sys.sp_addextendedproperty @name = N'MS_Description', @value = N'Short notes about this database.', @level0type = N'SCHEMA', 
@level0name = N'sqlinstances', @level1type = N'TABLE', @level1name = N'database', @level2type = N'COLUMN', @level2name = N'Notes'
GO

IF NOT EXISTS(SELECT  *
              FROM    ::fn_listextendedproperty(N'MS_Description', N'SCHEMA', N'sqlinstances', N'TABLE', N'database', N'COLUMN', N'Purpose'))
   EXEC sys.sp_addextendedproperty @name = N'MS_Description', @value = N'Short description of database purpose.', @level0type = N'SCHEMA', 
@level0name = N'sqlinstances', @level1type = N'TABLE', @level1name = N'database', @level2type = N'COLUMN', @level2name = N'Purpose'
GO

IF NOT EXISTS(SELECT  *
              FROM    ::fn_listextendedproperty(N'MS_Description', N'SCHEMA', N'sqlinstances', N'TABLE', N'database', N'COLUMN', N'LastUpdated'))
   EXEC sys.sp_addextendedproperty @name = N'MS_Description', @value = N'Last time this database was polled. Default is the insert date.', 
@level0type = N'SCHEMA', @level0name = N'sqlinstances', @level1type = N'TABLE', @level1name = N'database', @level2type = N'COLUMN', 
@level2name = N'LastUpdated'
GO

IF NOT EXISTS(SELECT  *
              FROM    ::fn_listextendedproperty(N'Description', N'SCHEMA', N'sqlinstances', N'TABLE', N'database', NULL, NULL))
   EXEC sys.sp_addextendedproperty @name = N'Description', @value = N'Database information for SQL Servers. Links to sqlinstances.sqlserver 
through ServerName and instance_name.', @level0type = N'SCHEMA', @level0name = N'sqlinstances', @level1type = N'TABLE', @level1name = 
N'database'
GO

IF NOT EXISTS(SELECT  *
              FROM    dbo.sysobjects
              WHERE   id = OBJECT_ID(N'[DF_database_LastUpdated]')
                      AND TYPE = 'D')
   BEGIN
         ALTER TABLE [sqlinstances].[database]
         ADD CONSTRAINT [DF_database_LastUpdated] DEFAULT(getdate()) FOR [LastUpdated]
   END

GO

Now you can see what I’ve created using these statements (staying in the MDW database):

SELECT 'sqlinstances.sqlserver' AS 'Table'
      , objname AS 'Column'
      , VALUE AS 'Description'
FROM   fn_listextendedproperty(NULL
, 'schema'
, 'sqlinstances'
, 'table'
, 'sqlserver'
, 'column'
, DEFAULT) ;
GO

SELECT 'sqlinstances.database' AS 'Table'
      , objname AS 'Column'
      , VALUE AS 'Description'
FROM   fn_listextendedproperty(NULL
, 'schema'
, 'sqlinstances'
, 'table'
, 'database'
, 'column'
, DEFAULT) ;
GO

In the next installment I’ll show you how I use a few queries to begin to tie the data together. I’ll then explain how to fill it in.

InformIT Articles and Sample Chapters

As I mentioned, you’ll need to ensure that you have maintenance on this database. You can read more about that in this previous Reference Guide entry

Books and eBooks

If some of these queries are new to you, or you need a refresher in the SQL language, definitely check out Sams Teach Yourself SQL in One Hour a Day, 5th Edition, by Ryan Stephens, Ron Plew, and Arie D. Jones.

Online Resources

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

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.

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