To install Acu4GL on a Windows server

  1. Install MSSQL.

    You must install and configure Microsoft SQL Server, version 6.5 or later, on the Windows server machine before you install Acu4GL for MSSQL on the client machine. Follow the instructions from your RDBMS vendor.

  2. Copy the Batch File.

    MS_INST.CMD is a batch file from Micro Focus that creates the MS_INST.SQL file, which is the collection of stored procedures necessary for executing Acu4GL. Copy MS_INST.CMD to your server machine into a directory of your choice.

  3. Execute the Batch File.

    To execute the batch file, enter

    MS_INST LockDatabase

    where LockDatabase is the database you want to use for the internal lock tables. This database is created if it does not already exist.

    Users must have write access to this database.

    The next step creates MS_INST.SQL, the collection of stored procedures necessary for executing Acu4GL for MSSQL.

  4. Install the Micro Focus Stored Procedures.

    To install the stored procedures in your Microsoft SQL database, execute the generated MS_INST.SQL file with the SQL Query Analyzer or the SQL Server Management Studio if you are using Microsoft SQL Server 2005.

    By default, the stored procedures are installed into the master database. However, you may choose another database in which to store them.

This completes the setup on the Windows server machine.

Note: If you are upgrading from an earlier version of Acu4GL, be sure to install the new stored procedures. Stored procedures are always upgraded 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 Acu4GL 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 master 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.