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 via user groups, you need to do this only once for all users of the group instead of repeating the procedure for each user.
Just create the required user groups in ARIS Administration and delete user groups that you no longer need.
Delete database languages that are no longer needed from the database and the configuration. If you do need one of the languages at a later time, you can create it again.
Create only those font formats that you need, and delete the ones you do not require.
Create only filters and templates that you need, and delete those you do not require.
Reduce the size and resolution of images and embedded objects (OLE 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 have piled up that no longer have any occurrences in any model, create a database backup and perform a reorganization. During the reorganization, all objects that no longer have occurrences in any model are deleted.
Use suitable model sizes. Very large models containing a large number of objects affect both 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 actually 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.