- This topic has 81 replies, 8 voices, and was last updated 1 year, 3 months ago by
.
-
Posts
-
There is a DB Export module that can write data to MSSQL.
We don’t have a plan to develop MSSQL archive (similar to ModArcPostgreSql, for example). It can be done by other developers, or we can implement MSSQL archive by a contract.Since now the ModArcPostgreSql are available, is there any planning on making configuration Database “BaseDAT” also stored in PSQL?
Then the users can change their passwords, admins can edit alarm threshold on the web .
Currently it is possible to upload the project to PostgreSQL https://ibb.co/TLdT8Zt
But project changes are stored as usual in XML files and later uploaded to the database. It would be interesting in the future to implement an alternative approach, edit project directly in the database. It would require fully new, web based Administrator app.You can find in ScadaInstanceConfig.xml the option to change file storage to PostgreSQL storage. If the PostgreSQL storage is selected, the Server app loads a project from the database.
Fully editable for all Configuration Database maybe not necessary. Partially editable maybe even better for admin to control the access of users.
e.g.
In the table view, the displayed channel can be check and edit for the alarm limits.But does it require restart of the scadaserver service to be effective after changing alarm limit settings if configuration stored in DB?
But does it require restart of the scadaserver service to be effective after changing alarm limit settings if configuration stored in DB?
Currently, yes. We need a special command to reload users and limits to avoid restart.
Limits are checked many times a second, so we can’t read them from the database every time, and should keep them in the memory cache.
- You must be logged in to reply to this topic.