Hi,

“Yes”, but doing it like that will not be officially supported. The application should be the only one writing to the database, however some consideration was made to enable reading the data directly from the database.

Also I would assume in practice the historian service component must be shut down before doing any changes, otherwise the results might be undefined. Plus note that nothing prevents setting values manually which might be otherwise limited by the UI, which might cause a scenario that the UI could stop working, show wrong data or cause some other undefined result. But if you just make it so that the database would look exactly same as-if written from the UI while both the Configurator UI + the service component are shut down everything like should work.

NOTE!
Do not edit the schema however, all tables and columns need to be as they are, they are versioned (via liquibase lib) and basically any changes not made by the application itself to the schema will most likely cause it to not start (and in practice the schema must be dropped or reverted to the state it was before so that it is the application itself making the changes). Also this would most likely happen much later than doing schema edits, i.e. if a newer version of the application needed to do changes, it must be itself the one doing them (it will do checksums etc.).