Best Approach for CrowdStrike Integration with ServiceNow SAM Using Service Graph Connector

[AkhilK247773814]

Hello,

We are planning to integrate ServiceNow with CrowdStrike to ingest data and automate Software Asset Management. The current approach is to use the Service Graph Connector to pull data into a staging table, retain the data for 5 days, and then move it to the Software Installation table through a scheduled job that runs weekly.

Could you please confirm if this approach is appropriate? Specifically, we would like to understand:

• Whether holding data in the staging table for a few days and processing it weekly could impact normalization or any downstream processes
• If there are any potential risks or performance concerns with this design
• Whether any other teams are working on any other implementations in the same instance gets impacted?

Please share your recommendations or best practices for implementing this requirement effectively.
Regards,
Akhil K

[dreinhardt]

HI @AkhilK247773814 

The ServiceNow platform, as well as the SG integrations themselves, provide built‑in capabilities to limit table growth. The platform includes table cleaners (for example, for staging tables), which typically have a default retention of seven days—please confirm this with your platform team. SG follows a similar approach and retains data based on either the number of imports or a defined number of days, depending on the table cleaner configuration.

You should align with the platform team on data retention policies, table cleaner settings, and related governance. I have seen customers with Intune or SCCM staging tables exceeding 70 million records because data was imported daily while cleanup only ran weekly.

• Whether holding data in the staging table for a few days and processing it weekly could impact normalization or any downstream processes

What is the use case for staging data for multiple days and only processing it once a week?

Looking at other inventory systems (such as SCCM or Intune), software installation data is imported without delay. This ensures that the software installation tables remain up to date and that removed software is deleted as soon as it is no longer included in the payload.

Best, Dennis