I think the subject of an all encompassing CMDB is a litte beyond what this forum was set up to provide.
We are more concerned with the specific area of database change management i.e. how changes to database schemas and data by developers/DBAs etc are reliably audited and deployed so that every "Configuration Item" that is part of a running system has a rock solid provenance. You should always be able to trace the origin of an object from cradle to grave.
Another function the database change management process should give you is the ability to build a database to ensure that no objects are broken.
regards,
Malcolm Leach www.innovartis.co.uk DB Ghost Build, Compare and Synchronize = Change Management for SQL Server |