You may want to delete historical performance data if the Uptime Infrastructure Monitor Archive process has timed times out and data older than the Archive Policy still exists in the data store. You You may also choose to manually delete historical performance data to free up the threads for regular monitoring that the Uptime Infrastructure Monitor Archive process would occupyoccupies. Another Another reason to manually delete historical performance data is to shrink the size of the DataStore.
- The first step is to verify the oldest data samples within the Datastore. Use Use the DataStore Profile script for a MS SQL database database found on the Support Portal's Tools & Utilities page.
Once you know the oldest data sample, go to the Historical Data Purge Scripts page and download the MS SQL trim script you want to run i.e. Ad-hoc or Use Archive Settings.
Warning WARNING: All deleted data will be lost. Ensure that you complete a full data store backup before proceeding with a trim script. - Choose a date for which all data samples collected before this day will be deleted. It is strongly recommended that deletions are completed in small chunks (e.g. 2 weeks or 1 month at a time) rather than attempting one large delete statement, so if the oldest data in the data store is from July 1, 20142016, choose July 15, 2014 2016 as the day to delete from.
- You can verify that the historical data has been deleted by running a performance graph or report in the Uptime Infrastructure Monitor GUI or simply running the DataStore Profile script again.
If you encounter any issues or have any questions regarding this process please do not hesitate to contact support@uptimesoftwareuptime-support@idera.com for guidance.
See related articles for DataStore running on MySQL or Oracle.