You may want to delete historical performance data if the Uptime Infrastructure Monitor Archive process has timed out and data older than the Archive Policy still exists in the data store. 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 occupy. Another reason to manually delete historical performance data is to shrink the size of the DataStore which is covered in the Shrinking your MySQL DataStore knowledge base article.

1. The first step is to verify the oldest data samples within the Datastore. Use the DataStore Profile script for a MySQL database found on the Suppo rt Portal's Tools & Utilities page.

2. Once you know the oldest data sample, go to the Historical Data Purge Scripts page and download the MySQL trim script you want to run i.e. Ad-hoc, Procedure or Use Archive Settings.

WARNING: All deleted data will be lost. Ensure that you complete a full data store backup before proceeding with a trim script.
3. 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, 2014, choose July 15, 2014 as the day to delete from.
4. You should verify the historical performance data has been deleted by running a performance graph or report in the Uptime Infrastructure Monitor UI 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 uptime-support@idera.com for guidance.
See related articles for DataStore running on MS SQL or Oracle.