Good day with everyone, I am working on a project that involves ignition and mysql workbench, however, since it is a new month, ignition generates a new table of the month, leaving the other data behind, how could I prevent this from happening and all the data is only stored in a single table, your support please.
You can disable partitioning on your history provider:
https://docs.inductiveautomation.com/display/DOC81/Tag+History+Providers#TagHistoryProviders-DatasourceHistoryProvidersSettings
Be warned that this will make a table that grows infinitely; pruning of old historical data operates on the entire table, so if you disable partitioning Ignition will never go in and delete old historical data for you, which can bog down your DB over time.
Ignition only does this on the history provider. It means that when you use Ignition's built-in history queries that they run much more quickly since they only have to query the months (or whatever time periods have been configured) between the start and end dates of the query.
If you are writing queries to read from the historian tables then I suspect that there is something wrong with your project structure or your understanding of how the historian works.
1 Like