Update the Configuration File for Microsoft SQL Server Datastores

Attention: This feature is in Early Adopter Product (EAP) release status. We will continue the development of additional features and provide additional interfaces via patch updates and future releases. Please contact Micro Focus SupportLine if you require further clarification.

Use these steps to create or update a configuration file that includes entries to one or more datastores.

If you do not already have a database configuration file (MFDBFH.cfg), in a text editor, create a simple text file and name it MFDBFH.cfg. If you already have a configuration file, open it and then skip to step 3.
Code the base element:
```
<datastores>
</datastores>
```
Add a <server> element for each database server instance you intend to connect to. Each <server> element contains 3 attributes:
Note: If you are editing a configuration file that already contains entries to the required server instance, skip to step 5.
- name - the name of the instance. An entry of (local) or localhost defaults to your machine name when the file is processed.
  Note: You can use an environment variable as the name of the data source: set a variable in your environment, and then use the following syntax:
```
<server name=$(env-name) type="sqlserver" access="odbc"/>
```
- type - the type of database; for Microsoft SQL Server databases this should be sqlserver
- access - the type of protocol for the database connection. Currently only odbc is supported.
For example, for a local Microsoft SQL Server instance:
```
<datastores>
   <server name="(local)" type="sqlserver" access="odbc">
   </server>
</datastores>
```
Next you need to specify the databases within the instance.
Firstly, you need to create a reference to the master database:
Note: If the <server> element for your database server instance already exists, this reference should already exist.
```
<datastores>
   <server name="(local)" type="sqlserver" access="odbc">
      <dsn name="<data-source>" type="database" dbname="master"/>
   </server>
</datastores>
```
Next, you need to add further <dsn> elements for each datastore. Each <dsn> element contains the following attributes:
- name - the name of the data source.
- type - the type of database. For datastores, this is type="datastore".
- dsname - the name to which Enterprise Server will refer to the datastore; this is the name specified as <datastore-name> when the ODBC data source was created for the database.
- optio - the optimizations that are applied to database file handling operations at run-time. The available options are none (no optimizations applied), or all (currently, this only applies for line-sequential files opened for input). If this attribute is not specified, no optimizations are applied.
- userid and password - a set of valid credentials used to access the database.
Note: On Windows, you may omit the userid and password attributes for local MSSQL installations that allow Windows (SSPI) authentication.
```
<datastores>
   <server name="(local)" type="sqlserver" access="odbc">
      <dsn name=<data-source> type="database" dbname="master" userid=<user> password=<pass>/>
      <dsn name=<data-source> type="datastore" dsname=<name> optio=<opt> userid=<user> password=<pass>/>
   </server>
</datastores>
```
Save the configuration file, ensuring it is named MFDBFH.cfg.

Example MFDBFH.cfg

The following is an example of a configuration file that contains two datastores, a region database and a cross-region database. The MSSQL server instance is also configured for Windows authentication, hence the omission of the userid and password attributes.

<datastores>
   <server name="(local)" type="sqlserver" access="odbc">
      <dsn name="SS.MYMASTER" type="database" dbname="master"/>
      <dsn name="SS.VSAM" type="datastore" dsname="VSAM"/>
      <dsn name="SS.SEQ" type="datastore" dsname="SEQ" optio="all"/>
      <dsn name="SS.CAS.ESDEMO" type="region.cas" region="ESDEMO" feature="all"/>
      <dsn name="SS.CROSSREGION" type="crossregion.cas"/>
   </server>
</datastores>

Next, you must use the dbfhdeploy command line utility to create the datastore and add files to it.