Want to re-run historical data collection job for Incidents? How do I clear out the old data?

John W5
Mega Expert

Want to control date range for historical data collection job for Incidents.  How can I delete the old content?   [Per Wednesday's bi-weekly mtg . . . I thought Isaak indicated this could be done; deleting several indicator at once.  Just don't do a whole bunch . . . as the system will take a performance hit]   Thanks

[UPDATE]    Looks like "if" you re-run a historical data collection job, it will "delete" the old content for you before creating the new entries.    Can someone please confirm that what I read in SN is correct for "Data collection process and logging - entry 13."?

1 ACCEPTED SOLUTION

Marcello Correa
ServiceNow Employee
ServiceNow Employee

Hi John,

You don't have to worry about deleting old PA scores when rerunning historical collection jobs, as ServiceNow will delete old score for those dates (please see image below).

find_real_file.png

 

IMPORTANT: Please be advised that running (or rerunning) historical jobs comes at a cost. Not every indicator will collect data correctly when running retroactively (e.g. indicators of number of records not updated in the last X days). Also, breakdowns on fields that would  have changed (e.g. assignment group, state) since the retroactive date will also collect an incorrect score (scores will reflect the current database value for that field instead of the value of that field at the retroactive date). Think twice before dropping old scores collected correctly through daily jobs and replacing them with new scores collected through historical jobs.

 

View solution in original post

3 REPLIES 3

Marcello Correa
ServiceNow Employee
ServiceNow Employee

Hi John,

You don't have to worry about deleting old PA scores when rerunning historical collection jobs, as ServiceNow will delete old score for those dates (please see image below).

find_real_file.png

 

IMPORTANT: Please be advised that running (or rerunning) historical jobs comes at a cost. Not every indicator will collect data correctly when running retroactively (e.g. indicators of number of records not updated in the last X days). Also, breakdowns on fields that would  have changed (e.g. assignment group, state) since the retroactive date will also collect an incorrect score (scores will reflect the current database value for that field instead of the value of that field at the retroactive date). Think twice before dropping old scores collected correctly through daily jobs and replacing them with new scores collected through historical jobs.

 

In other words, I did this so I'm screwed. I have run historical [PA_Incident] a few times back to back. Oh Lord, help me! 

John W5
Mega Expert

Thanks Marcello for taking the time to present this information.   I kind of had a hunch this would be the answer.  Further, we've just started with ServiceNow, having gone live December 10th, 2018.   So, the rerunning of historical jobs should have a "minor impact" on our data collection.   Although, the above points are duly noted as some collected information would be skewed due to this rerunning.   Take care,