To install Database Connectors for Microsoft SQL Server

Note: Your Microsoft SQL Server can be installed on a separate server, or on the same machine as your client. See the Microsoft SQL Server help for details on how to configure the relevant communications.

Install a supported version of Microsoft SQL Server.
You must install and configure Microsoft SQL Server, version 6.5 or later, on the Windows or Linux server machine before you install Database Connectors for MSSQL on the client machine. Follow the installation instructions from the vendor.
Copy ms_inst.cmd (Windows) or ms_inst.sh (Linux/UNIX) from the install (Windows), or /src/mssql (Linux/UNIX) sub-directory of your Micro Focus product installation directory to a directory on the server.
This is the batch file supplied by Micro Focus that creates the stored procedures necessary for using Database Connectors.
Execute the batch file using the following command:
ms_inst LockDatabase

where LockDatabase is the database you want to use for the internal lock tables; this does not need to be an existing database, as one will be created, if required, in the next step. However, you must ensure the required Database Connectors users have write access to this database.

Executing this command produces a ms_inst.sql file.
Execute the contents of this file (ms_inst.sql) using one of the appropriate database tools (such as SQL Query Analyzer or the SQL Server Management Studio on Windows, or the SQL Server command-line tools on Linux).
When complete, the stored procedures necessary for the MSSQL connector are installed.

This completes the setup on the server machine.

Note: If you are updating from an earlier version of Database Connectors, be sure to install the new stored procedures. Stored procedures are always updated in such a way that they are compatible with older versions of the product, so installing new stored procedures over old ones does not affect your ability to run with an older version of the interface software. Your new version of Database Connectors for MSSQL may not run properly without the corresponding stored procedures.

It can be difficult to maintain multiple copies of stored procedures; therefore, we recommend that you continue to create the stored procedures in the same database. If your installation does not permit this, you do have the flexibility to create the stored procedures elsewhere. However, to facilitate maintenance of the stored procedures, we recommend that you create as few databases as possible.