Is there any issue with having data pruning enabled on several ignition instances all pointed at the same database if they are all configured with the same time period?
or would the preferred method be to configure the database to prune this data itself?
Different Ignition gateways storing SQL historian data (not specified, but assuming that's what you meant since you mentioned 'pruning') will be storing data into entirely separate tables, based on the drvid assigned in sqlth_drv: Ignition Database Table Reference | Ignition User Manual
Unless you're doing something very bad and having multiple gateways with the exact same gateway name storing to the same database, which is firmly in the realm of "unsupported, unspecified behavior".
Thanks Paul, yes you are correct this is referencing SQL historian data.
I’ll investigate the configuration and review your comments
In the sqlth_drv table there are unique entries for each of our gateways. However, there aren’t unique tables per gateway, just sqlt_data_*partition date*.
Is that expected?
Scratch that! upon closer review I see now the drvid is a part of the SQL table!
so to answer my own question, When multiple gateways pointed at the same DB and are set to prune each gateway will delete its associated tables based on the drvid
Thank you for your guidance Paul!