SQL: Storing Data Dictionary Descriptions


DevX Home    Today's Headlines   Articles Archive   Tip Bank   Forums   

Results 1 to 2 of 2

Thread: SQL: Storing Data Dictionary Descriptions

  1. #1
    Steve Pierce Guest

    SQL: Storing Data Dictionary Descriptions


    SQL Server 7.0 has access to all the info that you could ever want about a
    database, table, or column by using the sys tables. The only thing lacking
    is a description.

    My company would like to access a data dictionary for all tables and columns
    in the company. The only thing that I cannot give them is a table level
    or column level description to describe purpose, updates, and the like.
    If I store these items on a seperate datadictionary database, I create quite
    a few problems when trying to create the relationships. If I use the db/tbl/col
    name as key, any changes to these values will orphan the description.

    Has anyone attempted anything like this before? Am I headed in the right
    direction?

    Thanks in Advance,
    Steve Pierce
    Senior Software Engineer
    The Carsley Group
    12200 East Thirteen Mile Road, Suite 100
    Warren, MI 48093
    VOICE: 810-573-8788 Extension 41
    FAX: 810-573-8988
    WEB: http://www.carsley.com
    EMAIL: spierce@carsley.com

    Share on Google+

  2. #2
    Rob Vieira Guest

    Re: Storing Data Dictionary Descriptions

    Usually, such information will be stored as part of your ERD if you're using
    a major design tool such as ErWin, ERStudio, or PowerDesigner.

    The good news is that description information was added to the metadata that
    you can associate with a table in SQL Server 2000 - both at the table and
    column level.

    --
    Rob Vieira
    Visit www.ProfessionalSQL.com Today. It's new and improved!

    "Steve Pierce" <spierce@carsley.com> wrote in message
    news:3a6eea6d$1@news.devx.com...
    >
    > SQL Server 7.0 has access to all the info that you could ever want about a
    > database, table, or column by using the sys tables. The only thing

    lacking
    > is a description.
    >
    > My company would like to access a data dictionary for all tables and

    columns
    > in the company. The only thing that I cannot give them is a table level
    > or column level description to describe purpose, updates, and the like.
    > If I store these items on a seperate datadictionary database, I create

    quite
    > a few problems when trying to create the relationships. If I use the

    db/tbl/col
    > name as key, any changes to these values will orphan the description.
    >
    > Has anyone attempted anything like this before? Am I headed in the right
    > direction?
    >
    > Thanks in Advance,
    > Steve Pierce
    > Senior Software Engineer
    > The Carsley Group
    > 12200 East Thirteen Mile Road, Suite 100
    > Warren, MI 48093
    > VOICE: 810-573-8788 Extension 41
    > FAX: 810-573-8988
    > WEB: http://www.carsley.com
    > EMAIL: spierce@carsley.com
    >



    Share on Google+

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
HTML5 Development Center
 
 
FAQ
Latest Articles
Java
.NET
XML
Database
Enterprise
Questions? Contact us.
C++
Web Development
Wireless
Latest Tips
Open Source


   Development Centers

   -- Android Development Center
   -- Cloud Development Project Center
   -- HTML5 Development Center
   -- Windows Mobile Development Center