If you did not configure direct connection strings, use the following steps to create ODBC data sources to access the region and cross-region databases.
There are a number of different driver managers that you can use to configure an ODBC data source. These instructions are carried out using unixODBC. If you are using a different driver manager, consult the vendor instructions for creating data sources.
(This may differ depending on the version of MSSQL you are running.)
[ODBC Driver 17 for SQL Server] Description=Microsoft ODBC Driver 17 for SQL Server Driver=/opt/microsoft/msodbcsql17/lib64/libmsodbcsql-17.2.so.0.1 UsageCount=1
[<datasource-name>] Driver = <driver-name> Server = <server-name> Database = master
[<datasource-name>] Driver = <driver-name> Server = <server-name> Database = <region-name>
[<datasource-name>] Driver = <driver-name> Server = <server-name> Database = _$XREGN$
The following is an example of an .odbc.ini configuration file that contains data sources for a local MSSQL database instance that stores files from the ESDEMO enterprise server region in a region and cross-region database.
[SS.MASTER] Driver = ODBC Driver 17 for SQL Server Server = localhost Database = master [SS.CAS.ESDEMO] Driver = ODBC Driver 17 for SQL Server Server = localhost Database = ESDEMO [SS.CAS.CROSSREGION] Driver = ODBC Driver 17 for SQL Server Server = localhost Database = _$XREGN$
The data sources for the region and cross-region databases are configured. Now, you can configure your enterprise server regions to use the databases.