Microsoft SQL Server

Make sure that ODBC data source is defined on database client and database server systems, with the correct ODBC driver. Note that Genero FGL provides different types of SQL Server drivers:
Important:
Configure your ODBC data source to use the appropriate Microsoft SQL Server driver.
- On Microsoft® Windows® platforms:
  - With the Microsoft ODBC 17 driver for SQL Server (MSODBCSQL17.DLL), use the dbmsnc_17 ODI driver.
    
    Minimum Microsoft ODBC for SQL Server version: 17.6.
  - With the Microsoft ODBC 18 driver for SQL Server (MSODBCSQL18.DLL), use the dbmsnc_18 ODI driver.
- On Linux® platforms:
  - With Microsoft ODBC 17 driver for SQL Server, use the dbmsnc_17 ODI driver.
    
    Minimum Microsoft ODBC for SQL Server version: 17.6.
  - With Microsoft ODBC 18 driver for SQL Server, use the dbmsnc_18 ODI driver.
  - With FreeTDS ODBC (http://www.freetds.org/files/stable/), use the dbmftm_0 ODI driver.
    
    Minimum FreeTDS version: 1.00.104.
  - With Easysoft ODBC for SQL Server, use the dbmesm_1 ODI driver.
    
    Minimum Easysoft ODBC for SQL Server version: 2.0.19.
Important:
By default, Microsoft ODBC 18 for SQL Server enables connection encryption, that can lead to the following ODBC error when TLS/SSL certificates are not properly configured:
```
[Microsoft][ODBC Driver 18 for SQL Server]SSL Provider: [error:1416F086:SSL routines:
tls_process_server_certificate:certificate verify failed:self signed certificate]
```
To disable encryption on Linux platforms, set the following ODBC option in the data source definition file:
```
Encrypt = No
```
On Microsoft Windows, set "Connection Encryption" to "Optional" in the 4th panel of the ODBC data source configuration application.
On Windows platforms, the PATH environment variable must define the access path to database client programs (ODBC32.DLL). On UNIX platforms, check database client software documentation for environment settings (LD_LIBRARY_PATH, ldconfig).
On Windows, check the SQL Server Client configuration with the Client Network Utility tool. Verify that the ANSI to OEM conversion corresponds to the execution of applications in a CONSOLE environment.
Make sure the database client locale is properly defined. On UNIX platforms, check that the client character set parameter of the ODBC data source corresponds the locale used by the application (LANG/LC_ALL).
On Windows, you can make a connection test with the Microsoft Query Analyzer tool. On UNIX, see client software documentation for available SQL command tools (isql command line tool for example).