This article explains how to delete historical data from an up.time MS SQL datastore. See related articles for MySQL and Oracle data stores. The tables listed in the article are valid for up.time 7; although the logic applies to any release of up.time, you may receive errors for tables that do not exist.
You may want to delete historical data if the up.time 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 data to free up the threads for regular monitoring that the up.time Archive process would occupy. And another reason to manually delete historical performance data is to shrink the size of the data store which is covered in the Shrinking your MySQL DataStore knowledge base article.
For ease, a stored procedure that accomplishes the same as the statements below is available by contacting Support at [email protected].
| Warning |
|---|
These commands are permanent. All deleted data will be lost. Ensure that you complete a full data backup before proceeding with these commands. |
...