Simple definition
A CMDB (Configuration Management Database) records configuration items in an information system and the relationships between them.
Technical definition
A CMDB stores structured information about Configuration Items (CIs), such as servers, applications, network devices, services, contracts, locations, and other relevant components. Its value comes not only from CI attributes but also from relationships that describe service dependencies.
How it works / role
Its role is to provide a trusted view of assets and dependencies for support, change management, impact analysis, incidents, and problems. It is useful only when the data remains sufficiently accurate and current.
What is it used for?
Identify components affected by an outage or change, understand ownership and dependencies, and improve traceability across the information system.
Practical example
Before changing a core switch, the team checks the CMDB to identify dependent servers, VLANs, and business services so it can evaluate the change impact.
Common issues
- Outdated or duplicate CIs
- Missing or inaccurate relationships between components
- Automatically discovered data is not reconciled with manual records
- CMDB is treated as a simple inventory without dependency modeling
Key takeaway: The value of a CMDB depends less on the number of stored objects than on the accuracy of data and relationships that support operations.