Property settings for CMDB Query Builder
Summarize
Summary of Property settings for CMDB Query Builder
These properties allow ServiceNow administrators withsncmdbadminoradminroles to configure the behavior and performance of the CMDB Query Builder. Settings control query result limits, execution timeouts, batch sizes, table exclusions, and query execution modes. Adjusting these properties helps optimize query processing, improve scalability, and tailor the query environment to organizational needs.
Show less
Key Properties and Their Practical Use
- Maximum Results Limit (glide.cmdb.query.maxresultslimit): Caps the number of records returned in scheduled queries and when loading all results in the Query Builder. Default is 10,000, helping manage system load and avoid excessive data retrieval.
- Batch Time Limit (glide.cmdb.query.batchtimelimitinsec): Defines the maximum time (in seconds) allowed to process one batch of 100 query results. Default is 300 seconds, balancing query responsiveness with workload.
- Overall Query Time Limit (glide.cmdb.query.querytimelimitinsec): Sets the total time limit for completing an entire query. Default is 1800 seconds, preventing excessively long-running queries.
- Non-CMDB Table Exclusions (glide.cmdb.query.noncmdb.blacklistedtables): Enables exclusion of specified non-CMDB tables from appearing in the Query Builder. Supports comma-separated lists and wildcard patterns, allowing cleaner query building focused on relevant tables.
- Batch Size (glide.cmdb.query.batchsize): Controls the number of records processed per batch when saved queries run. Default value is 100, helping regulate resource usage during query execution.
- Default Execution Mode (glide.cmdb.query.executionmode): Specifies which query engine to use when running saved queries without a defined execution mode. Options include V1 (legacy engine) and V2 (enhanced engine optimized for performance and scalability). Default is V2.
- OR Execution Mode (glide.cmdb.query.orexecutionmode): Determines the execution engine for queries containing logical OR operators. It takes precedence over the default execution mode and affects output format. Options are the same as above, with V2 as the default.
Key Outcomes for ServiceNow Customers
- Fine-tune query performance and system resource consumption by adjusting result limits, timeouts, and batch sizes.
- Enhance query relevance and usability by excluding non-essential tables from the Query Builder interface.
- Leverage improved query engines to handle complex queries efficiently, especially those with logical OR conditions.
- Maintain control over query execution behavior to prevent long-running queries that could impact platform performance.
- Ensure a better user experience for CMDB administrators by customizing query settings to fit organizational scale and complexity.
Set property values to configure query processing.
Access and Role required
| Property | Description |
|---|---|
| Limits the number of results for a scheduled query and in the results section in the Query Builder when you select Load All Results. glide.cmdb.query.max_results_limit |
|
| Time limit (in seconds) for running one batch to get one batch of query results (100 results). glide.cmdb.query.batch_time_limit_in_sec |
|
| Time limit (in seconds) for running an entire query to get all results. glide.cmdb.query.query_time_limit_in_sec |
|
| Exclude list of non-CMDB tables. The specified tables will not appear in the CMDB Query Builder when a user creates a query. glide.cmdb.query.non_cmdb.black_listed_tables |
|
| glide.cmdb.query.batch_size |
Batch size allocated globally when saved queries run.
|
| glide.cmdb.query.execution_mode |
Default execution engine to use when running a saved query when the query's execution mode isn't set (Query Execution Mode is 'None'). Used in combination with other settings to determine which engine execution mode to use for running a query.
|
| glide.cmdb.query.or_execution_mode |
Default execution engine to use for queries that contain at least one logical OR operator. This property also affects which output format to use, which is distinctively different between the V1 and V2 modes. This property is used in combination with other settings to determine which engine execution mode to use for running a query, and has precedence over the glide.cmdb.query.execution_mode system property.
|