Following table lists the tasks which can be performed on the HDB along with the required privileges.

Tasks

Privileges needed

Tools

Creation of HDB

Launch SMC with a user as a member of the sysadmin fixed server role.

 

Note: It is not possible to create the HDB without using SMC.

SMC only

Backup of database

This can be executed either from SMC, from Desigo CC Client or outside by calling an internal stored procedure.

 

The backup file will include the HDB database and all CURRENT archive databases.

Transaction log is not included.

 

In case of recovery model simple it is recommended to configure schedule backups.

 

From SMC:

Launch SMC either with a user as a member of the sysadmin fixed server role OR with a user having HDB owner privileges on the HDB to be backed up. Configure GMS service with a user having HDB owner privileges on the HDB.

 

From Desigo CC Client:

Configure GMS service with a user having HDB owner privileges on the HDB.

 

Outside SMC:

Configure GMS service with a user having HDB owner privileges on the HDB.

 

Can be executed from outside SMC by running following SQL statement on the HDB database:

 

EXEC invokingBackup

Backup gets created in the path configured in SMC.

 

EXEC invokingBackup @destination = 'C:\GMSDatabases\Backups\HDB.bak'

 

Backup gets created in the specified path.

 

Note: This stored procedure will queue the backup task and will be executed by the maintenance task in background. It is not recommended to backup the HDB without using SMC or without using Desigo CC Client or without using this stored procedure for following reasons:

  1. HDB has a lot of internal system tables which needs to be synchronized after a restore.
  2. HDB runs automatically some event-driven and resources intensive jobs in the background. It could have consequences if then in parallel a backup is created.
  3. A backup performed by the internal procedure has some header information which ensures the consistency of the backups in the file and which is mandatory for a restore via SMC.

SMC,

Desigo CC Client,

3rd party tools

Backup of transaction log

This task is handled internally.

Configure GMS service with a user having HDB owner privileges on the HDB.

 

For details please refer following section on “Getting the HDB online after disaster”.

 

Backup of transaction log can be done but it should not truncate the transaction log, otherwise it would harm Desigo CC’s fail-safe-strategy. Also be aware that Desigo CC’s fail-safe-strategy makes automatic backups of the transaction-log and truncates it from time to time and this would interfere and harm the customer backup strategy.

None

Restore of database

Launch SMC with a user as a member of the sysadmin fixed server role.

 

The restore of database is possible only with backups taken from SMC, Desigo CC Client and the backups from stored procedure but not with the backups present in the recovery log path.

 

Note: It is not recommended to restore the HDB without using SMC for following reasons:

  1. HDB has a lot of internal system tables which needs to be synchronized after a restore.
  2. HDB backup might consist of more than one database.
  3. There are some jobs in the internal queue when the backup was created which need to be stopped.

SMC only

Restore of transaction log

For details please refer following section on “Getting the HDB online after disaster”.

None

Configuration of HDB (database size, long term storage configuration, etc.)

Launch SMC either with a user as a member of the sysadmin fixed server role OR with a user having HDB owner privileges on the HDB to be configured.

 

Note: It is not possible to configure the HDB without using SMC.

Database size (mdf, ldf), autogrowth options should not be changed from outside and should be changed from within SMC only.

Special note on autogrowth settings.

Autogrowth settings should not be changed otherwise it would result in an undefined behavior. No manual changes of autogrowth is allowed.

a) For example, autogrowth for mdf file should not be enabled, otherwise the settings stored in the HDB and the actual HDB size would get inconsistent resulting in undefined behavior of the maintenance operation which takes care that the database never expands the size of the history database. If the database size (mdf, ldf) has to be increased, it should be changed from within SMC only. HDB is a short term storage (STS) and the old data gets deleted once the fill level increases to 90% of the total size of the history database. If the data has to be permanently stored, long term storage (LTS) has to be enabled from SMC.

b) For example, autogrowth for ldf file should not be disabled, as at times some transactions may need additional space in the transaction log before the transaction log delete tasks get triggered which recycles the transaction log, and if the autogrowth is disabled such transactions would fail and may result in data loss.

SMC only

Upgrade of HDB

Launch SMC either with a user as a member of the sysadmin fixed server role OR with a user having HDB owner privileges on the HDB to be upgraded.

 

Note: It is not possible to upgrade the HDB without using SMC.

SMC only

Mount archives

Launch SMC either with a user as a member of the sysadmin fixed server role OR with a user having HDB owner privileges on the HDB.

 

Note: It is not possible to mount the archives without using SMC. Also see Step 5.2 below on needed privileges for the maintenance HDB service user.

SMC only

Maintenance of HDB

Configure HDB service with a user having HDB owner privileges on the HDB.

 

Note: Maintenance of HDB is done by HDB service and it requires advanced privileges which can be removed if required by following the steps mentioned in this document.

SMC only

Table 1: Tasks performed on HDB, required privileges and tools

 

 

Getting the HDB online after disaster

For recovery model simple:

The user must use SMC to restore from any of the previous backups.

 

For recovery model full:

The user can choose to restore on a test system the latest backup from the recovery log path (either HDB-A.BAK or HDB-B.BAK).

 

In addition try to create a backup on the crashed system of transaction log (HDB.TRN) from the transaction log file (HDB.ldf) present in the log file path and try to apply it on the above restored database.

 

Refer to section “Full Data Backup“ in Desigo CC SMC online help for recovery steps.

 

Then on please contact support to bring this database online.

 

Note:

Please refer version specific documentation of this document to see for changes between major versions if any. This document is intended for MP4.0 only.