Micro Focus Enterprise Developer 3.0 for Visual Studio 2017 > Programming > Mainframe Programming > HCO for SQL Server (HCOSS) > Before Using HCO for SQL Server

Before Using HCO for SQL Server

Describes the SQL Server database adjustments that are required each time you upgrade your version of Enterprise Developer.

HCOSS mimics z/OS functions and other z/OS functionality by storing SQL Server stored procedures and tables in your SQL Server database(s).

To successfully use HCOSS, it is important that you update this information stored in your database(s) each time you upgrade your version of Enterprise Developer, including new releases, updates, or hotfixes. Doing so ensures that HCOSS always executes optimally.

We provide three HCOSS scripts you can use to update your SQL Server database(s) after each upgrade. By default, all are located in your %ALLUSERSPROFILE%\Micro Focus\Enterprise Developer\hcoss directory:

InstallSYSIBM.sql: Creates metadata tables.
InstallBindProcs.sql: Creates SQL Server stored procedures required for binding and managing temporary table metadata.
InstallDigitsFunction.sql: Creates SQL Server stored procedures required to support DB2 z/OS functions.

To execute these scripts against any SQL Server database, you must have the following permissions to the database:

CREATE SCHEMA
CREATE PROCEDURE
EXECUTE PROCEDURE in the SYSIBM schema

We suggest that you choose from the following methods of script execution:

SQL Server Management Studio

Execute all three HCOSS scripts against each SQL Server database.

SQL Server sqlcmd utility

This option enables you to automate the process, running the three scripts consecutively. Use the following syntax at a command prompt:

sqlcmd -S myServer\instanceName -i "scriptDir\HCOSSscript.sql"

Where:

`myServer`	Name of a SQL Server database
`instanceName`	SQL Server instance name
`scriptDir`	Full path to the directory that contains the scripts
`HCOSSscript`	Name of an HCOSS script

DSN Bind Utility

While the DSN Bind utility does just what the other two options also do, you might find it easier to use as an alternative to executing the scripts yourself. We recommend this procedure:

Start an Enterprise Developer command prompt.
Do one of the following:
- If using Windows authentication, enter:
```
DSN SYSTEM(connectionName)
```
- If using SQL Server authentication:
```
DSN SYSTEM(connectionName) ASUSER(LoginID.Password)
```
Where connectionName is the name of a connection created with the HCOSS Manage Connections tool, and LoginID and Password are a SQL Server login ID and password respectively.

DSN automatically executes the required scripts and updates the database. The command window shows its execution process.
When a DSN command prompt appears, enter END.

Note: You must have the same SQL Server permissions when using the DSN Bind utility as are required to execute the scripts using one of the other methods.