The Change Management Database (CMDB) Only Works When it's Up to Date

The Change Management Database (CMDB) Only Works When it's Up to Date

• 21 Jan 2012
• Written by: Evolven

Tom Kearns explains that the entire idea of having a CMDB is to have a single, definitive resource for the configuration of all IT assets.

The concept is great but the unfortunate reality is that many times we don't have a single CMDB and it is not always up-to-date and accurate. He explores the concept of what happens if the CMDB is not accurate, saying that it could deliver information that would provide access to the wrong asset, dooming the problem to never being fixed. 

There are also a lot of changes happening that need be recorded in the CMDB and when changes occur, the CMDB is usually updated after-the-fact. That leaves an information accuracy gap that gets repeated over and over again.

Source: http://www.tditechnologies.com/the-change-management-database-cmdb-only-works-when-it%E2%80%99s-up-to-date-and-accurate

 Want to learn about  a totally new approach to configuration and change management?  

Learn how Evolven redefines configuration and change management with its Change Monitoring solution. Take our tour or sign up for a free trial and see for yourself how Evolven eliminates outages. Really.