Database schemas in a multi developer environment

In the case of multiple developers developing Ignition vision projects that will all need to be merged into a final gateway encompassing a new facility, is there any advantage or disadvantage to enforcing everyone to use a single Historian DB schema or better to allow each project to have its own historian DB, and create all the various schemas as projects are imported? The DB is MSSQL on its own VM. Id prefer to keep one name for management purposes (one config for purge, backups,etc), but if there is some efficiency to be gained by splitting across multiple schemas within a MSSQL DB, I can pivot.

Friendly bump

I would make one database connection with one schema, unless you have a more significant reason than just developer convenience.

1 Like