...

Sometimes it happens that we revert to the last backup of the D2000 Configuration database. This restore is usually performed on a notebook where D2000 is installed, using D2000 Application Manager. Then, we use the restored database to XML export the configuration of objects that have been deleted or modified, and to revert changes.

Please provide a list of database users used for accessing D2000 databases (Configuration, Logging, Archiving) as well as to external databases (MES)

Configuration/Logging databases: Only the D2000 Server accesses these databases. Fixed username "dba" is used for access, password is configurable.

The Configuration database is read when the D2000 Server is started. The whole contents (with the exception of object history) is read into the D2000 Server's memory. After that, all configuration changes (including startup values) are written to the Configuration database. Reading is performed only when working with the Object modification history.

The Logging database is read whenever a user/script needs logging data. Both reading and writing are performed only by the D2000 Server. Writing is performed continuously, as events in the system occur.

So, whenever a user/script needs logging data, the D2000 Server reads it. Therefore, user PCs don't need network connectivity to the configuration database, only to the D2000 Server (TCP port 3119).

Archiving database: Only the D2000 Archiv process accesses these databases. Fixed username is used for access ("dba" for PostgreSQL and Sybase SQL Anywhere, <application>_archiv for Oracle), password is configurable.

Both reading and writing are performed only by the D2000 Archiv. Writing is performed continuously, as values of D2000 objects are being changed, and values can also be written by script (or manually by users from D2000 HI processes).

Again, user PCs don't need network connectivity to the archiving database, only to the D2000 Server (TCP port 3119), which routes the read/write requests to the respective D2000 Archiv process (there can be a single one or multiple instances in redundant systems). 

External databases (e.g., MES): Connectivity to external databases is handled by the D2000 DbManager process. It uses DSN/username/password configured in the Database object. Non-administrators don't have access to the configuration of these objects, so they don't know these parameters.

Again, user PCs don't need network connectivity to the external databases, only to the D2000 Server (TCP port 3119), which routes the read/write requests to the respective D2000 DbManager process.

Note 1: Sometimes, however, users have, e.g., Microsoft Excel reports that directly read data from these databases; in these cases, network connectivity is required, but not because of the D2000 system, but because of these reports. Best practice is to use a dedicated, read-only user for these reports, who has strictly limited access rights for specific database tables only.

Note 2: Sometimes, external systems read/write data from/to these databases; in these cases, network connectivity is required from these systems. Best practice is to use a dedicated (if possible, read-only) user for these reports, who has strictly limited access rights for specific database tables only.