--- sourceDocument: Brazil ServiceNow AI Platform Capabilities sourceDocumentLink: https://www.servicenow.com/docs/r/servicenow-platform Release : - brazil ft:locale : - en-US ft:publication_title : - Brazil ServiceNow AI Platform Capabilities ft:clusterId : - platcap bundleId : - platcap workflow : - Platform --- # Explore # Exploring CMDB Query Builder {#ariaid-title1} Release version: Brazil Updated September 10, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 4 minutes to read Summarize ![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete. ## Summary of Exploring CMDB Query Builder The CMDB Query Builder in ServiceNow allows you to create complex queries across multiple Configuration Item (CI) classes, non-CMDB tables, and varied relationships. It features a drag-and-drop canvas where you select CI classes and define relationships and logical operators (AND/OR) to build detailed infrastructure and service queries. This tool helps you analyze and manage your CMDB data efficiently, enabling use cases such as identifying hardware with specific software, mapping virtual to physical servers, or assessing costs per application service. Show full answer Show less ## Key Features * **Query Canvas:** Drag CI classes onto the canvas, set one as the starting node (the first class added), and define relationships and logical operators for query construction. * **Query Types:** * **CMDB Query:** Focuses on CI classes and their relationships, optionally incorporating related non-CMDB tables like Asset, Task, and Problem. * **Service Mapping Query:** Targets application services within service maps, supporting both direct and multi-level indirect relationships. * **Combination Query:** Combines CMDB and Service Mapping queries to refine results, such as finding CIs connected to specific services or excluding services. * **Intelligent Search Integration:** Integrated natural language query (NLQ) allows you to build queries using everyday language. Intelligent Search parses input and generates valid queries on the canvas for further refinement or execution. * **System Controls:** The Intelligent Search feature can be enabled or disabled via the system property `glide.cmdb.query.nlq.activated`. The list of non-CMDB tables available for queries can be controlled through `glide.cmdb.query.noncmdb.blacklistedtables`. * **AI Search and NLQ Genius Results:** Complementary tools that provide natural language search capabilities to find CMDB records directly from portals or workspaces, enhancing discovery without accessing the Query Builder. ## Practical Use and Benefits * Build precise queries to understand infrastructure relationships and dependencies across your CMDB and related records. * Use saved queries to populate CMDB groups, then leverage APIs to retrieve and act on CI lists collectively. * Combine various query types to analyze application services, identify unmapped servers, evaluate technology costs, and investigate incidents related to specific CIs or services. * Utilize natural language input to simplify query creation, reducing the need for complex query syntax knowledge. ## Important Considerations * The starting node in a query must be unique and cannot be changed once set; it must be the only node connected directly to a logical operator. * Complex queries that improperly connect multiple nodes to the starting node's operator will fail to execute, prompting you to revise the starting node. The CMDB Query Builder enables you to build complex infrastructure and service queries that span multiple CMDB classes, non-CMDB tables, and that involve many CIs that are connected by different relationships. The CMDB Query Builder provides a canvas into which you drag the CI classes that you want to include in a query. Then you add relationships, AND/OR operators between the CI classes, and define the relationship properties to query for. You can use saved queries to populate a CMDB group with CIs, and then use scriptable APIs to retrieve the CI list and apply actions collectively to all the CIs in the group. There are two query types: CMDB Query and a Service Mapping query, which you can use separately or in combination to create queries such as: * All hardware in my service offering that has Windows installed. * All CIs of a certain type in an application service. For example, all Apaches/Web Servers/Linux servers per service. * All virtual servers and the physical servers that host them. * All servers that are not mapped to any application service. * All application services and their associated servers and the cost of each server. This query helps evaluate the cost of technology for each application service. {#querying-cmdb__ul_pwh_mlc_rw} Starting node: The starting point of the query which is labeled as STARTING NODE on the Query Builder canvas. The first class that you drag to the canvas becomes automatically the starting node of the query and you cannot select a different starting node. In a complex query, the starting node must always be the only node connected to an AND/OR operator. If you try to connect a second node to an operator that the starting node is connected to, the query fails to run and a prompt to select a different starting node appears. ## Additional information {#querying-cmdb__section_lbh_y2m_nwb} For a webinar, see [CMDB Query Builder Queries and Reporting - Platform Analytics Academy](https://www.servicenow.com/community/performance-analytics-blog/platform-analytics-academy-october-19th-2022-cmdb-query-builder/ba-p/2351259) blog post in the ServiceNow Community. ## Intelligent Search for CMDB integration {#querying-cmdb__section_ixd_dkd_gsb} By default, [Intelligent Search for CMDB](https://www.servicenow.com/docs/Lc9nJoQvlCqv2RcFpw1oGg "Use everyday natural language query (NLQ) in a search string to query for a set of CIs in the CMDB. Intelligent Search for CMDB, parses, resolves ambiguities, and converts your search string into a valid CMDB query. Complex search strings open fully constructed on a canvas of CMDB Query Builder where you can continue and refine, or run.") functionality is integrated into the CMDB Query Builder. When opening the Query Builder, you can use the Intelligent Search search box which appears above the Query Builder canvas. Intelligent Search lets you use everyday natural language query (NLQ) to build a query. Intelligent Search parses, resolves any ambiguities in table names and relationship types, and then converts your search string into a valid query. The query appears fully constructed on the Query Builder canvas where you can run or continue and develop the query. The integration of Intelligent Search for CMDB with the CMDB Query Builder is controlled by the system property glide.cmdb.query.nlq.activated, which is set to true by default. If you set the property to false, Intelligent Search for CMDB will not be available within the Query Builder. ## AI Search and CMDB {#querying-cmdb__section_a35_xnq_f1c} NLQ Genius Results for [AI Search](https://www.servicenow.com/docs/access?context=overview-ais&version=brazil&pubname=brazil-platform-administration&ft:locale=en-US) use natural language queries to find CMDB tables that match your search without leaving a portal or workspace. For more information, see [NLQ Genius Results](https://www.servicenow.com/docs/access?context=genius-result-nlq-ais&version=brazil&pubname=brazil-platform-administration&ft:locale=en-US). Note: AI Search is a complementary search experience that allows you to surface CMDB records in your normal flow of work, without having to access the CMDB Query Builder. It doesn't replace intelligent Search for CMDB, which is purpose-built and integrated into CMDB Query Builder. ## Query types {#querying-cmdb__section_i4q_thy_l3c} There are several types of CMDB queries: CMDB Query : A query type that queries the infrastructure for CI classes and the relationships and references that connect them. You can optionally add the context of non-CMDB tables to a CMDB query. You can include [Service instances (Application services)](https://www.servicenow.com/docs/cWo535dQmOp8g7DR_9RWXg "Understand service instances (application services), learn about different application service types and how multiple ServiceNow business units and products use them.") in a CMDB query, to find, for example: * All critical application services in your database. * All infrastructure in a particular application service. * All incidents for a particular CI in an application service, or all incidents for all the CIs of an application service. * All application services with a pattern of a service connected to a database, and where the database has incidents. {#querying-cmdb__ul_g2p_yhy_l3c} The list of available non-CMDB tables includes a subset of tables within the system, which have a reference to the Configuration Item \[cmdb_ci\] class or its children. The list of non-CMDB tables, includes tables such as Asset, Task, and Problem. You can use the system property [glide.cmdb.query.non_cmdb.black_listed_tables](https://www.servicenow.com/docs/EWe6cbQnLqGN~DTOYAM1HQ "Set property values to configure query processing.") to narrow down the list of non-CMDB tables to choose from. Service Mapping Query : A query type that queries application services. The query is framed within an application service map. You define a pattern, and query for application service maps that have that pattern in their definition. The relationships in Service Mapping queries are matched by single-level direct relationships which is similar to the CMDB queries, and in addition, they are also matched by multi-level indirect relationships if they exist. A query for a relationship between two CI classes is satisfied even if the two CI classes are connected by intermediate CI classes that are not specified in the query. Combination Query : You can combine the two query types by incorporating a saved Service Mapping query into a CMDB query. For example, create a CMDB query for Windows Servers that are connected to Tomcat WAR. Then connect the Tomcat WAR CI class to a Service Mapping query. The query changes to find Windows Servers that are connected to Tomcat WAR which is included in the services that returned by the Service Mapping query. You can inverse that query by choosing Does Not Belong To Service. This changes the query to find Windows Servers that are connected to Tomcat WAR that is not included in services returned by the Service Mapping query. **Related concepts** * [CMDB groups](https://www.servicenow.com/docs/QCsUKjt2xi_MTBGn4D8oFg#cmdb-groups "A CMDB group is a collection of CIs that lets you apply CI actions collectively to all the CIs that are members in the group.")