Mostly, in-house rules or procedures do not allow the SGLC administrator to undertake the administrative tasks of the database administrator. Therefore, the automated update of the database from the SGLC administration has been removed and has been replaced by the independent application
Furthermore, the function “referential integrity” is used when updating to prevent invalid entries, which can lead to problems. This was implented a few versions ago.
A consequence is that the following situations might occur when updating the existing database. Normally this will be seen through an interruption of the program CreateTables.exe with the error message 0x1.
- Parts of the database are created with an incorrect scheme-name. This happens because different standard values as DB owner are used in CreateTables (standard scheme-name from the SQL server configuration) and the SGLC administration (“dbo”).
- A refresh of the database cannot be undertaken because the referential integrity is damaged. It might be that the database to be migrated contains faulty links between the single tables because of technical faults in older versions. To prevent this, SGLC has used the referential integrity to secure the consistency of data. For a successful migration it is necessary to bring the database to a consistent status.
More information regarding referential integrity can be found here :
If the issues described above occur, please follow the instructions in the downloadable pdf Database errors and create tables errors.