SG-SCCM Computer Identity: Occasional inconsistent data load

Dean C
Tera Contributor

‎02-10-2025 02:31 PM

Hello all,

 

Our SN instance is running into an occasional issue where the SG-SCCM Computer Identity data source pulls a significantly smaller number of records compared to normal during its daily scheduled runs.

For example, within the Concurrent Import sets, a normal load would bring in about 48k records, but when the issue occurs, it can be much smaller, such as in the hundreds (our last issue pull was at around 5200).

The Data Source for "SG-SCCM Computer Identity" has the "Use last run datetime" field set to FALSE, making me think that this should be doing a full load.

Interestingly, we have two instances that are pulling from the same source and configured the same, and are scheduled just only 15 minutes apart. When one instance brought in a small amount, the other instance still loaded the expected amount.

 

Is there some sort of configuration either on the SN or SCCM side that would randomly cause this to occur?

Apologies that I cannot upload screenshots at this moment.

Any advice or pointers would be appreciated.

 

Thanks!

0 Helpfuls
  • 339 Views
1 REPLY 1

Kieran Anson
Kilo Patron

‎02-11-2025 04:38 AM

The SQL database could be truncating information...but I'm not an expert in that area to know where to advise.

 

In terms of ServiceNow, The "probe" on the MID server that pulls data will send the retrieved information in batches of 200 records. You can check ecc_queue to view the input. The MID server logs would also indicate whether the connection was terminated early either between the instance and the MID, or MID and the SQL server. 

 

Couple things to check:

  1. Are there records in ecc_queue that have errored? This would indicate the data was retrieved but not passed to the import set
  2. Are there the expected number of ecc_queue response records? Each contains 200 records, so 48k/200 = amount of records expected
  3. The MID writes the results of running a JDBC import to agent\work\monitors\ECCSender. Files in here could be an indication of something broken/crashed/errored as the file should be deleted once sent to ServiceNow.
  4. Further details on MID processing
  5. Enable debugging on the MID - This might be hard as leaving debug on for extended period of times can produce large log files. But the additional logging could provide further context to your issue
0 Helpfuls