I am using a MSSQL database to store my tag history. This database sync its data with another MSSQL database using transactional replication.
Ignition is setup to for monthly partitioning of its tag history data to the MSSQL DB.
The problem I am having is, once I do the initial setup of the Distribution, Publication and Subscription, the Articles (DB tables I wish to sync) are static. Every month, a new table is created in the database but the Publication initially created does not contain the new table (Article).
The new article can be added to the subscription manually using Management Studio but that is not an option.
Removing tag history partitioning would prevent this issue but having a single table for tag history will cause problems later down with performance.
Is there a way to automate the process of adding the new tag history table in the database to an existing publication or possibly even create a new publication and subscription containing that new table automatically with no user intervention?