--- title: Improved query performance with direct field population in CI tables description: 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. locale: en-US canonical_url: https://www.servicenow.com/docs/r/australia/it-operations-management/discovery-and-service-mapping-patterns/query-service-account-ldc-fields.html release: australia product: Discovery and Service Mapping Patterns classification: discovery-and-service-mapping-patterns topic_type: concept last_updated: "2026-03-12" reading_time_minutes: 4 keywords: [cloud CI tables, Service Account, Logical Datacenter, query performance, cloud discovery] breadcrumb: [Discovery patterns used by ITOM Visibility, ITOM Visibility, IT Operations Management] --- # Improved query performance with direct field population in CI tables 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 and Logical Datacenter 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. \[Omitted image "multi-joins-vs-direct-fields.png"\] Alt text: Comparison between complex multi-table joins without the feature versus direct field access with the feature For information about enabling this feature, see [Enable direct field population for query performance](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-operations-management/discovery-and-service-mapping-patterns/populate-service-account-ldc-fields.md). ## System properties
| Property | Description |
|---|---|
| **sn\_itom\_pattern.populate\_saldc.stale\_job\_threshold\_days** | Sets the number of days after which a running job is considered stale and automatically canceled. For more information, see [Set the Populate Service Account and LDC job stale threshold](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-operations-management/discovery-and-service-mapping-patterns/configure-sa-ldc-stale-days.md).- **Type**: Integer - **Default value**: 2 |
| **sn\_itom\_pattern.populate\_saldc\_full\_resync** | Starting with Discovery and Service Mapping Patterns version 1.35.0, determines if all CI records are reprocessed on the next job run. For more information, see [Trigger a full CI table resync for direct field population](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-operations-management/discovery-and-service-mapping-patterns/configure-sa-ldc-full-resync.md).- **Type**: Boolean - **Default value**: False |