What we need is the ability to assign different Partition Table Lengths and Pruning periods (History Provider configurations) to various machine equipment. To do this today, requires a separate database for each Data Partitioning/Pruning (History Provider Config) requirement as it (would appear) you can NOT apply different History Providers to the same database (i.e. there is only a one to one relationship between History Providers and Database Connections, even though you can configure multiple History Providers on the same Database Connection).

This would allow for finer control over when partition tables are created and pruning activities performed on a database.

Possible route to a solution:

If we have one database and multiple History Providers names created pointing to the same database, shouldn't there be separate Partition tables generated for each of the different History Providers based on the sqlth_drv table? It seems that the sqlth_drv is using the combination of the Gateway name and the Tag Provider (why?) name to uniquely identify the Partition Tables with the 'ID' field being used in the Table name, but shouldn't this be the combination of the Gateway and the History Provider Name. This would make more sense and allow for multiple History Providers to use the same database with different Partition Sizes and Pruning configurations.

Additional details are discussed in support: https://support.inductiveautomation.com/hc/en-us/requests/80323?page=1