SCCM - Service Graph Connector
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-29-2025 05:30 AM
Does anyone have experience using the SCCM Service Graph Connector with large data sets such as 700K computer systems and 60M Software Install records?
Questions are:
- Can the SGC handle that volume?
- How long should you expect the import to run?
- Is the v_FullCollectionMembership table critical to the data load and what does it hold that the Software Install or Computer System do not. Ask the question as it is significantly larger than the other tables.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-29-2025 06:51 AM
Hi @JRobbi ,
As per my understanding, below solution is probably help you on this.
1. Can the SGC handle that volume?
Yes — the Service Graph Connector (SGC) can technically handle large data sets like that; it was designed for enterprise-scale environments.
However, practical performance depends heavily on:
* MID Server capacity & network bandwidth
* Database and SCCM performance (how fast SCCM responds to queries)
* ServiceNow instance size & indexing
* Whether you are running a full import or delta import
For very large data sets, ServiceNow generally recommends incremental / delta loads instead of frequent full loads to keep things performant.
2. How long should you expect the import to run? This varies a lot based on:
* Size of data
* MID Server specs
* Network latency
* SCCM database performance
* Whether it's a first-time full load or incremental load
In real-world large environments, a full load could easily take many hours (often several hours to even a full day for the initial import).
After that, incremental loads (delta syncs) typically take much less time (minutes to a couple of hours depending on data change volume).
To optimize:
* Increase number of transform threads (with caution)
* Ensure MID Servers are scaled up (CPU, RAM)
* Optimize SCCM SQL views and indexes (especially for big tables like v_FullCollectionMembership)
* Use multiple MID Servers if your architecture allows
3. Is the v_FullCollectionMembership table critical, and what does it hold?
Yes, it is quite important.
* v_FullCollectionMembership is a mapping table that links each resource (like computers) to one or more collections in SCCM.
* It helps identify which devices belong to which collections (e.g., device collections for deployment targeting, security compliance, etc.)
It doesn’t hold actual software install data or direct device data, but rather:
* Membership: "Device X is part of Collection Y"
* Enables building software deployment context, targeting, and compliance views
Because many enterprises have thousands of collections, and each device can belong to many collections, this table can get very large — often much larger than the number of devices themselves.
Best Practices when using SCCM SGC for large data:
* Use delta loads whenever possible
* Stagger large imports to off-peak hours
* Optimize SCCM SQL views and indexes (especially on big tables)
* Monitor Import Set Run and Transform logs for errors or bottlenecks
* Use multiple MID Servers for load balancing if architecture supports it
* Review and trim unnecessary data from SCCM if possible (e.g., old collections, stale software installs)
Please appreciate the efforts of community contributors by marking appropriate response as Mark my Answer Helpful or Accept Solution this may help other community users to follow correct solution in future.
Thank You
AJ - TechTrek with AJ - ITOM Trainer
LinkedIn:- https://www.linkedin.com/in/ajay-kumar-66a91385/
YouTube:- https://www.youtube.com/@learnitomwithaj
Topmate:- https://topmate.io/aj_techtrekwithaj (Connect for 1-1 Session)
ServiceNow Community MVP 2025
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-29-2025 09:48 AM
Thanks for the information....figured much of the same on the mids, capacity, etc. But, regarding the collection membership, how is the sgc using that data to manage in the cmdb...simply for the collection membership data? I am unclear the use case on who would want the collection data in the CMDB and can you share the table it would load that data into?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-30-2025 07:33 AM
Hi @JRobbi ,
As per my understanding, That will be probable solution you are looking for , Correct me if I am wrong here
1. Lets Understand How SGC uses collection membership data in CMDB
When you integrate with a source system (like Intune, SCCM, JAMF, etc.) via Service Graph Connector, the connector can bring in:
* The CI (computer/device, etc.)
* And also collections / groups / tags that the CI belongs to in the source system.
This “collection membership”:
* Helps to logically group CIs (e.g., “All laptops in Finance department” or “Windows 11 rollout group”).
* Supports use cases like:
* Dynamic assignment groups
* Targeted software deployments
* Impact analysis in change management
* Reporting (e.g., how many devices are in a certain compliance group)
2. Where does SGC load collection data in the CMDB?
In ServiceNow, collection membership usually loads into two places:
Data Table
The collection itself (like a device group) cmdb_ci_collection (or sometimes a more specific table extending it)
Membership relationship between a CI and the collection cmdb_ci_member
So effectively:
* The collection (e.g., a group in Intune or SCCM) becomes a CI of type cmdb_ci_collection.
* The link showing which CIs are members of which collections is stored as relationship records, typically in cmdb_rel_ci or directly as records in cmdb_ci_member.
3. Why do customers want this in CMDB?
Even if not everyone needs this, some real use cases:
* Software deployment targeting: “Deploy only to CIs in a certain collection.”
* Risk / compliance: Identify which devices belong to a high-risk collection.
* Operational dashboards: View device health or patch status by collection.
* Impact analysis: If a planned change affects a collection, you know which devices are impacted
Please appreciate the efforts of community contributors by marking appropriate response as Mark my Answer Helpful or Accept Solution this may help other community users to follow correct solution in future.
Thank You
AJ - TechTrek with AJ - ITOM Trainer
LinkedIn:- https://www.linkedin.com/in/ajay-kumar-66a91385/
YouTube:- https://www.youtube.com/@learnitomwithaj
Topmate:- https://topmate.io/aj_techtrekwithaj (Connect for 1-1 Session)
ServiceNow Community MVP 2025