Manage databases

Database administrators manage all of a tenant's databases.

Please note:

Database administrators and database users can take certain measures to ensure that the size and performance of databases are optimized.

If you observe basic factors from the start, you can optimize a database's size in terms of content. This results in faster database operations, such as backup and restore. Furthermore, administrative tasks become significantly easier. Consider this example: If you assign or change access privileges through the user groups, you do this only once for all users of the user group, instead of repeating the procedure for each user.

  • Just create the required user groups and delete user groups that you no longer need.

  • Delete database languages that are no longer in use from the database and the configuration. If a language comes back in use, you can create it again.

  • Create only those font formats that you use and delete the ones you do not require.

  • Create only the filters and templates that you use, and delete the ones you do not require. The Filters are not stored in the databases but will users to work only with the items they require.

  • Assign users access privileges to users through the user groups.

  • Reduce the size and resolution of images and embedded objects. For example, you can insert large logos in models and reduce their display size later, but they still take up the space required for their original size. If models with logos are versioned, the logos even take up this space in the database multiple times.

  • Distribute objects in different groups. For example, this makes sense because the group structure of a database reflects organizational structures of an environment. In this case, it makes no sense to save all object in the main group, for example. Database operations are faster if each group contains up to 1000 objects.

  • Therefore, it is recommended that you keep only objects that you really need in the database. If objects that no longer have any occurrences in any model have piled up, create a database backup and reorganize. During the reorganization, all objects that no longer have occurrences in any model are deleted.

  • Use suitable model sizes. The large size of a model that contains many objects affects both the model legibility and performance.

  • Modeling

    • Use occurrence copies if you want to use the same object in different models.

    • Use variants only for models and objects that differ. When creating model variants, you can decide which objects are to be created as a new variant, for which objects existing variants are to be used, and for which objects occurrence copies are to be created.

  • Versioning

    • Version only models that must be versioned. If you version the entire database every time, it becomes very large.

    • Do not create versions to save intermediate results. For this, we recommend database backups.

    • Delete versions you no longer need.