- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-14-2019 03:12 PM
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."?
Solved! Go to Solution.
- Labels:
-
Performance Analytics

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-14-2019 03:35 PM
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).
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.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-14-2019 03:35 PM
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).
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-04-2021 01:07 PM
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!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-15-2019 06:06 AM
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,