I was wondering if anyone has any ideas on how I could go about triggering a stored procedure right before a history table gets dropped by the pruning system. It would be a nice option to actually add to pruning setup on the gateway.
We partition daily and prune monthly. So what we would like to do is instead of just dropping all that data for each day we want to be able to run a SP that will “compress” that data into an “Summary” table that would give us daily Min, Max, Mean, STDEV and so on for each tag that is logged. We then can use this table to develop some base lining for specific machines over a much greater time.