--- sourceDocument: Yokohama IT Operations Management sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/yokohama/it-operations-management Release : - yokohama ft:locale : - en-US ft:publication_title : - Yokohama IT Operations Management ft:clusterId : - itom bundleId : - itom workflow : - Technology --- # Improved query performance with direct field population in CI tables # Improved query performance with direct field population in CI tables {#ariaid-title1} * Release version: Yokohama * * Updated January 29, 2026 * * ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read The Populate Service Account and LDC IN CMDB scheduled job populates the Service Account and Logical Datacenter fields in cloud configuration item (CI) tables, and the Virtual Machine Object field in the Hardware \[cmdb_ci_hardware\] table. This direct population reduces query complexity and improves query performance. Cloud Service Account (such as AWS Account, Azure Subscription, or GCP Project) and Logical Datacenter (such as AWS, Azure, or GCP Regions) information is stored separately from cloud CIs. To retrieve account or datacenter information for a cloud resource, queries require joins across multiple tables, including the relationship table that connects CIs. Similarly, Virtual Machine Object information is stored separately from the Hardware CI, requiring additional joins to retrieve data from the Virtual Machine Object \[cmdb_ci_vm_object\] table. With potentially millions of records in the relationship table, these joins could increase query time for teams working with cloud infrastructure data. Starting with the Discovery and Service Mapping Patterns version 1.30.2, you can enable a feature that denormalizes cloud CI tables by populating the Service Account \[cloud_service_account\] and Logical Datacenter \[logical_datacenter\] fields directly in cloud CI tables. The scheduled job also references tables extended from the Virtual Machine Object \[cmdb_ci_vm_object\] table via the Virtual Machine Object reference field in the Hardware \[cmdb_ci_hardware\] table. Populating these fields directly reduces the need for complex joins, supporting more efficient queries for reporting, analytics, and operational workflows involving cloud resources. After you enable this feature, Discovery populates these fields for both existing and newly discovered CIs. Figure 1. Query process with and without field population For information about enabling this feature, see [Enable direct field population for query performance](https://servicenow-prod.fluidtopics.net/Mtv_gzH2PisJvt4rvH3VJA "Populate Service Account, Logical Datacenter, and Virtual Machine Object fields in configuration item (CI) tables to improve query performance."). ## Supported Cloud CI tables {#query-service-account-ldc-fields__section_supported_tables} Service Account and Logical Datacenter fields are added to the following cloud CI tables: {#query-service-account-ldc-fields__table_cloud_ci_tables__entry__2} | Table label | Table name | |-|-| | Cloud Subnet | cmdb_ci_cloud_subnet | | Cloud Network | cmdb_ci_network | | Virtual Machine Instance | cmdb_ci_vm_instance | | Hardware Type | cmdb_ci_compute_template | | Cloud Hardware Type | cmdb_ci_cloud_hardware_type | | Compute Security Group | cmdb_ci_compute_security_group | | Image | cmdb_ci_os_template | | Cloud Image | cmdb_ci_cloud_os_image | | Cloud Load Balancer | cmdb_ci_cloud_load_balancer | | Cloud Resource | cmdb_ci_cmp_resource | | Cloud File Service | cmdb_ci_cloud_file_service | | Cloud Mgmt Network Interface | cmdb_ci_nic | | Endpoint | cmdb_ci_endpoint | | Cloud Function | cmdb_ci_cloud_function | | Cloud Object Storage | cmdb_ci_cloud_object_storage | | Cloud Gateway | cmdb_ci_cloud_gateway | | Database Instance | cmdb_ci_db_instance | | Cloud DataBase | cmdb_ci_cloud_database | | DynamoDB Table | cmdb_ci_dynamodb_table | [Table 1. Cloud CI tables with Service Account and Logical Datacenter fields] {#query-service-account-ldc-fields__table_cloud_ci_tables} ## Supported virtual machine tables {#query-service-account-ldc-fields__section_wgj_zk5_23c} The following virtual machine tables are referenced in the Virtual Machine Object \[cmdb_ci_vm_object\] field in the Hardware table: {#query-service-account-ldc-fields__table_f4l_cl5_23c__entry__2} | Table label | Table name | |-|-| | Windows Server | cmdb_ci_win_server | | Linux Server | cmdb_ci_linux_server | [Table 2. Referenced virtual machine tables] {#query-service-account-ldc-fields__table_f4l_cl5_23c} * **[Enable direct field population for query performance](https://servicenow-prod.fluidtopics.net/Mtv_gzH2PisJvt4rvH3VJA)** Populate Service Account, Logical Datacenter, and Virtual Machine Object fields in configuration item (CI) tables to improve query performance. **Previous topic:** [Activate a disabled pattern](https://servicenow-prod.fluidtopics.net/R5W5GP640V_5uNIhVNRPCw "If you want to use a pattern for discovery that's disabled by default, activate it manually.") **Next topic:** [Enable direct field population for query performance](https://servicenow-prod.fluidtopics.net/Mtv_gzH2PisJvt4rvH3VJA "Populate Service Account, Logical Datacenter, and Virtual Machine Object fields in configuration item (CI) tables to improve query performance.") **Related reference** * [Linux discovery](https://servicenow-prod.fluidtopics.net/tbWHQ8W2tJRHRooeehDOHA "Discovery and Service Mapping applications use probes and patterns to discover and map information about Linux computers and servers. The information is populated in the CMDB. Discovering some of these resources may require updating to the latest version of the Discovery and Service Mapping Patterns application from the ServiceNow Store.") * [Windows discovery](https://servicenow-prod.fluidtopics.net/f_Q~qP_q0vUp0GkIy~BTAQ "Discovery identifies and classifies information about Windows computers that use IPv4 addresses, IPv6 addresses, or both.")