Hi, I'm Ask INFA!
What would you like to know?
ASK INFAPreview
Please to access Ask INFA.

Table of Contents

Search

  1. Introduction to ODBC Connector
  2. ODBC connections
  3. Synchronization tasks with ODBC Connector
  4. Mappings and mapping tasks with ODBC Connector
  5. Pushdown optimization (SQL ELT)
  6. Data type reference

ODBC Connector

ODBC Connector

Configuring the Microsoft ODBC driver to connect to Microsoft Azure SQL Data Warehouse

Configuring the Microsoft ODBC driver to connect to Microsoft Azure SQL Data Warehouse

Before you establish an ODBC connection to connect to Microsoft Azure SQL Data Warehouse, configure the ODBC driver.
  1. Install the Microsoft ODBC drivers for Windows and Linux operating systems. To download the drivers, see https://docs.microsoft.com/en-us/sql/connect/odbc/linux-mac/installing-the-microsoft-odbc-driver-for-sql-server#microsoft-odbc-driver-131-for-sql-server.
  2. Before you can run tasks to connect to Microsoft Azure SQL Data Warehouse using the ODBC connection from Linux, you must set the ODBCINI and LD_LIBRARY_PATH environmental variables for the driver and create the DSN entries. Add the path of the
    odbc.ini
    file to the ODBCINI environment variable.
    setenv ODBCINI "/data/home/adputf_9/cloud_td/ODBCINI/odbc.ini"
  3. To set the LD_LIBRARY_PATH environment variable, use the following syntax:
    setenv LD_LIBRARY_PATH "/opt/microsoft/msodbcsql/lib64/libmsodbcsql-11.0.so.2270.0"
  4. Add entries for the Microsoft Azure SQL Data Warehouse data sources in the
    odbc.ini
    file.
    The following section shows a sample entry in the
    odbc.ini
    file:
    [Sample Azure DW ODBC DSN] [SD_Azure_DW] Driver=/opt/microsoft/msodbcsql/lib64/libmsodbcsql-11.0.so.2270.0 Description=Microsoft ODBC Driver 11 for SQL Server Server=dghhgx2ad3.database.windows.net Database=INFASQLDW_DEV LogonID=infadwadmin Password= QuotedId=Yes AnsiNPW=Yes EncryptionMethod=1 SeedBeforeConnect=1 EnableQuotedIdentifiers=1 ValidateServerCertificate=0 DriverUnicodeType=1
  5. Restart the Secure Agent.

0 COMMENTS

We’d like to hear from you!