Installation of Microsoft ODBC Driver 17 or 18 for SQL Server is required.

This Microsoft ODBC Driver 17 or 18 for SQL Server is compatible with the 2019 versions of SQL Server. See corresponding Microsoft articles for more details:

Download it from Microsoft download website:

On a client computer running HOPEX, it is recommended to ping the RDBMS server with a filled buffer to have an evaluation of the infrastructure. To do this, download the hrPING freeware tool available at https://www.cfos.de/en/ping/ping.htm. To use this tool, you must first accept the terms of the licence. Use it with the following command in a command window from a computer that will be running HOPEX:

Example for this command output:

If the value returned for “RTTs of replies in ms/avg” (0.535 in the example) is higher than 1 ms, contact MEGA. See hrPING help for details on this command.

The following sections will help your database administrator (DBA) size the Database server according to the profiles and the number of HOPEX users you plan to use.

Each new object takes up 30 KB on a disk (object with its attributes and links).

If you activate the HOPEX Repository Log file each action on the HOPEX repository creates an object.

You should reserve 5GB on the server disk.

Reminder:

HOPEX will stop working if the datafile is full. To avoid this, the databases can be created with the autoextend property activated. If this is not possible, the datafiles growth must be monitored carefully in order to provide more space if fullness is about to be reached.

This information will help you define the amount of memory (RAM) required for the database instance used to run HOPEX on the database server

One connection is used for each RDBMS storage. It means that, when a HOPEX User is connected to HOPEX, two connections to SQL Server are open (one for the SystemDb and one for the User repository).

An additional connection is used for each RDBMS storage when you use the HOPEX locks.