Click here to Skip to main content
13,548,686 members
Click here to Skip to main content
Add your own
alternative version


107 bookmarked
Posted 5 Sep 2004
Licenced CPOL

SqlDoc: Document your SQL Server Database

, 5 Sep 2004
Rate this:
Please Sign up or sign in to vote.
A small command prompt utility to help you document your SQL Server/MSDE database

Sample Image - sqldoc.gif


This article presents a small command prompt utility to help you document your SQL Server/MSDE database.


In SQL Server, every property of tables, fields, relations, etc. are stored in a few system tables. You can query those tables to extract information about your database. SQL Server provides a mechanism to simplify the queries to those system tables: Information Schema.

Try to run the command "SELECT * FROM INFORMATION_SCHEMA.columns" in any database. A list of every column in every table in the database will be returned.

I code this utility to auto document my databases, extract table names, columns names, field types, lengths, and nullable columns, and generate a HTML file with that information. You can tweak the queries to extract any other information that you need.

There is a special piece of information that is not available through Information Schema: column's description field. I find it very useful to fill that field when I design a table, to clarify the purpose of a column. To extract that description, you must bypass Information Schema and query directly the system tables.

How It Works

The inner working of this app is very simple. It gets the results of special queries, and writes an XML file which is used in combination with an XSLT file to produce the final HTML file.

Using the Code

You can quick test the utility, extracting information about the Northwind database, typing:

SqlDoc.exe -E -d northwind

This will produce the file output.html.

I've tried to mimic the OSQL command switches. The available switches are:

  • -E - uses integrated security to connect SQL Server
  • -S server_name - connects to a specific server
  • -U user_id - connects using a user name
  • -P password - self explained
  • -o outputFileName - self explained

The source code is very simple to follow and it's self-describing.

Note that as commented before, in order to extract the column's description field, the code bypasses the standard way to extract columns information. This means that in future releases of SQL Server, the query could fail. If you don't find the 'description field' useful, you can comment/uncomment these lines to use the method you want.

// most compatible way to retrieve column info but lacks 
// description field
//private const string SQL_GETFIELDS = "SELECT TABLE_NAME, " +

// this one gets columns info + the description field
private const string SQL_GETFIELDS = 
    "syscolumns.Id, AS COLUMN_NAME, " + 
    " AS DATA_TYPE, syscolumns.length" + 
    "sysproperties.[value] AS COLUMN_DESCRIPTION,  " +
    "syscomments.text as COLUMN_DEFAULT, " +
    "syscolumns.isnullable as IS_NULLABLE " +
    "FROM syscolumns INNER JOIN systypes " +
    "ON syscolumns.xtype = systypes.xtype " +
    "LEFT JOIN sysobjects ON = " + 
    "LEFT OUTER JOIN sysproperties ON " +
    "(sysproperties.smallid = syscolumns.colid" + 
    " AND = " +
    "LEFT OUTER JOIN syscomments ON syscolumns.cdefault = " +
    "WHERE IN " + 
    "(SELECT id FROM SYSOBJECTS WHERE xtype = 'U') " + 
    "AND ( <> 'sysname')" +
    "ORDER BY syscolumns.colid";

Points of Interest

Leaving apart the purpose of this app, I was interested in learning about the XSLT transformations. Included in the demo project is a test XSLT file. You can edit this file in order to improve the output format.


SQL Server stores tons of information about each database, relations, key columns, views, stored procedures, etc. So fully documenting the database, it's the way to go.


This article, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)


About the Author

Jose A. Gonzalvo
Web Developer
Spain Spain
Software developer

You may also be interested in...


Comments and Discussions

-- No messages could be retrieved (timeout) --
Permalink | Advertise | Privacy | Terms of Use | Mobile
Web01 | 2.8.180515.1 | Last Updated 6 Sep 2004
Article Copyright 2004 by Jose A. Gonzalvo
Everything else Copyright © CodeProject, 1999-2018
Layout: fixed | fluid