SQL Server data dictionary

[Gresford]

How would I create a data dictionary using the MS_Description column
in the extended properties and the information_schema columns? I
would like to include table name, column name, data type, null/not
null, and ms_description.

Has anyone done this or created a data dictionary in SQL Server any
other way before?

[Gresford]

Thanks! It worked perfectly!!

[--CELKO--]

>How would I create a data dictionary using the MS_Description column in the extended properties and the information_schema columns? <<

This is a start, but a data dictionary also has info about external
things, too. You need the domain, constraints, check digit formulas
or regular expressions, the trusted source that defines it, the type
of scale used, etc.

Then you need a way to get this stuff to the developers so they can
ignore it :)

[Roy Harvey (SQL Server MVP)]

On Wed, 27 Aug 2008 09:48:00 -0700 (PDT), --CELKO--
<jc*******@earthlink.netwrote:

>>How would I create a data dictionary using the MS_Description column in the extended properties and the information_schema columns? <<

This is a start, but a data dictionary also has info about external
things, too. You need the domain, constraints, check digit formulas
or regular expressions, the trusted source that defines it, the type
of scale used, etc.

To say nothing of the idea that a good DD should allow you to document
something before it has any physical existence. Today you first must
create the Customers table before you can define CustomerNumber or
CustomerName, or any of the other columns that make up the table. Yet
you can't create the table until you know the definitions of the
columns of the table.

Roy Harvey
Beacon Falls, CT

[--CELKO--]

>To say nothing of the idea that a good DD should allow you to document something before it has any physical existence. Today you first must create the Customers table before you can define CustomerNumber or CustomerName, or any of the other columns that make up the table. Yet you can't create the table until you know the definitions of the columns of the table. <<

Good point! I have not looked at commercial products in years, but
there ought to be one that will walk you thru some of things with a
dialog. DB Examiner will check the schema after the fact to look for
basic design flaws like repeated groups, bad names, etc.

[Paul Connelly]

In article <5g********************************@4ax.com>, SQL Server MVP
<ro********@snet.netwrote:

On Wed, 27 Aug 2008 09:48:00 -0700 (PDT), --CELKO--
<jc*******@earthlink.netwrote:

>How would I create a data dictionary using the MS_Description column in
the extended properties and the information_schema columns? <<

This is a start, but a data dictionary also has info about external
things, too. You need the domain, constraints, check digit formulas
or regular expressions, the trusted source that defines it, the type
of scale used, etc.

To say nothing of the idea that a good DD should allow you to document
something before it has any physical existence. Today you first must
create the Customers table before you can define CustomerNumber or
CustomerName, or any of the other columns that make up the table. Yet
you can't create the table until you know the definitions of the
columns of the table.

Wasn't that part of the reason for CREATE DOMAIN?

Which Microsoft apparently does not want to implement...