We have recently partitioned our database after switching to X-large 96 Profile as it requires Partitioned Database. Mai know the differences between Maully Deletion of HIgh Resolution data & Auto purge measure during cleanup task.
How does they affect by enabling or disabling for a partitioned database.
Answer by Peter K. ·
1. "Manually manage deletion of high resolution data" is mandatory when you have partitioning enabled. You mustn't switch it on if you don't have partitioning. In other words, check that box if and only if you have partitioning enabled. When checked on, it prevents the nightly clean-up task from deleting data from the high-res table.
2. "Auto purge measures during clean up task" is a choice that you have regarding our handling of splittings: The pwh schema has a large lookup table (called "dynamic_measure") that contains all the splittings of all the measures of your appmon system. This checkbox will make the clean-up task drop all splittings that haven't received data in 2 months (by default, linked to the mid-res retention time). These old splittings will therefore not be chartable anymore. If you choose to disable that checkbox, the dynamic_measure table will rgow indefinitely which may cause problems for larger installations with a high number of dynamic splittings, but you'll be able to chart all your historical splittings forever, even though they didn't get an update in months.
Answer by Trevor M. ·
The mentioned check box should not delete low-res data.
If you are interested in retaining low res data, make sure you keep the Never purge low res... box checked. Otherwise, you can uncheck it and set a time frame to keep this data.