What is CMDB in ServiceNow?
The CMDB (Configuration Management Database) is ServiceNow’s central record of your IT environment: servers, applications, databases, network devices and cloud resources, plus how they depend on each other.
How the CMDB works
Every item in the CMDB is a configuration item (CI). CIs are stored in tables that all extend the base table cmdb_ci, so a Linux server, a Windows server and a database instance each have their own class with the right fields, while still sharing common ones like name, owner and operational status.
What makes the CMDB valuable is relationships, stored in cmdb_rel_ci. A web application “Runs on” a server, which “Depends on” a database. Because ServiceNow knows these links, it can tell an agent which business services are affected when a server goes down, and tell a change manager what could break before a change is approved.
How data gets into the CMDB
Very little CMDB data should be entered by hand. Most of it comes from Discovery, Service Graph Connectors (for tools like Microsoft Intune, SCCM or cloud providers) and import sets. All of these sources pass through the Identification and Reconciliation Engine (IRE), which matches incoming data to existing CIs, prevents duplicates and decides which source is allowed to update which field.
A practical example
An alert arrives saying db-prod-07 is unresponsive. Event Management links the alert to the database CI, the CMDB shows that three application services depend on it, and the incident is created with the correct business service, priority and assignment group, before anyone has opened a ticket.
Best practices
Start with the CIs that support your most important services rather than trying to discover everything at once. Follow the Common Service Data Model (CSDM) so your services, applications and infrastructure are modeled in a way the rest of the platform understands. Give each CI class a clear owner, and review the CMDB Health dashboard regularly: it scores completeness, correctness and compliance so you can see where data is decaying.
Common mistakes
Loading data from many sources without reconciliation rules leads to duplicates and conflicting values. Treating the CMDB as a one-time project is the other classic mistake: without automated discovery and ownership, accuracy drops within months and people stop trusting it.
Frequently asked questions
Is the CMDB the same as an asset inventory?
No. Asset management tracks financial and contractual details such as cost, warranty and contracts. The CMDB tracks the technical and operational view: what a component does and what depends on it. In ServiceNow, assets and CIs are linked so you can see both views.
Do I need Discovery to use the CMDB?
Not strictly, but without automated sources the CMDB is hard to keep accurate. Discovery, Service Graph Connectors and integrations with existing tools are the usual ways to keep it current.
What is CMDB Health?
A set of dashboards and scheduled jobs that measure how complete, correct and compliant your CMDB data is, so you can find and fix gaps.
Related ServiceNow terms
Need help with CMDB or anything else in ServiceNow? We’re here with practical solutions that fit your organization and your teams.
Browse all 100 ServiceNow terms
ServiceNow is a trademark of ServiceNow, Inc. This glossary is an independent resource by Sequal Consultancy and is not affiliated with or endorsed by ServiceNow, Inc.