Generalities
Unsupported HOPEX Features in RDBMS Storage
When a HOPEX repository is stored on an RDBMS, HOPEX does not support the following features:
• MySQL RDBMS
• Oracle RDBMS
• Offline mode
• Repository protection
• Mixed environments
o MEGA proprietary format (GBMS storage format) repository and repositories stored on an RDBMS. For example, a GBMS environment (SystemDb) and one or more repositories stored on SQL Server. The opposite is also not supported (SQL Server environment with GBMS repositories within).
Expected Advantages
The advantages expected from an RDBMS deployment are:
• Compliance with company-wide IT standards.
• Guarantee of scalability and security.
• Quicker dispatch time. In particular with “big” HOPEX private workspaces (HOPEX private workspaces with many creations/deletions/updates).
With this type of architecture, HOPEX supports global deployment on the same repository. In particular, it enables bypassing some limits related to the GBMS storage format.
• Maximum limit of 510 concurrent private workspaces per environment. No limit is identified in the HOPEX application for SQL Server storage format.
• Maximum limit of 24 GB of data per HOPEX repository. No limit is identified in the HOPEX application for SQL Server storage format.
With the RDBMS storage format, the HOPEX environment contains unshared files. All the data accessed during the execution of the HOPEX application is stored in the RDBMS. The RDBMS guarantees scalability and security.
Licensing
The “HOPEX repository storage (SQL Server)” product is required on the license to gain access to the RDBMS storage feature. The license can be dedicated to the workstation or shared by a group of users. All users connecting to HOPEX must have access to this license as well as to other products (HOPEX IT Architecture…).