Hello
I have a system that fluctuates a lot on how much data is being recorded through historian. I sadly also have limited storage capacity and quite a large requirement on how long data needs to be recorded.
Pruning works great for keeping record for as long as I need. However, I will likely run out of storage before that time hits. The storage reaching capacity is perfectly fine, I just need to react, fire some alarms, and handle deleting some of the data to make space for newer information.
From what I understand from reading some of the documentation and some forum posts I should be able to delete a the sqlt_data_some_date table in my database, along with removing the entry in sqlth_partitians (with a script that does the oldest one etc...).
I was wondering if anyone knew if their were going to be any problems with said solution and if they had any other possible solutions I could look into. I thought about potentially having a script that changes the pruning date so that ignition prunes it for me. I just didn't know if that was more ideal or even possible. (And yes, I wish I could just increase drive space and hopefully this will end up happening in the future 
).
Anyway any feedback/advice would be appreciated!