Skip to main content Skip to complementary content

ODBC data connections

You can create a data connection to select data from an ODBC data source that has already been created and configured in the ODBC Data Source Administrator dialog in Windows Control Panel.

See: ODBC

Creating a new ODBC data connection

Do the following:

  1. Click Create new connection and select ODBC.

    The Create new connection (ODBC) dialog opens.

  2. Select which data source to use from the list of available data sources, either User DSN or System DSN.

    System DSN connections can be filtered according to 32-bit or 64-bit.

    For User DSN sources you need to specify if a 32-bit driver is used with Use 32-bit connection.

  3. Add Username and Password if required by the data source.
  4. If you want to use a name different from the default DSN name, edit Name.
  5. Click Save.

The connection is now added to the Data connections, and you can connect to, and select data from the connected data source.

Editing an ODBC data connection

Do the following:

  1. Click @ on the ODBC data connection you want to edit.

    The Edit connection (ODBC) dialog opens.

  2. You can edit the following properties:

    Select which data source to use from the list of available data sources, either User DSN or System DSN.

    Username

    Password

    Name

  3. Click Save.

The connection is now updated.

Warning noteThe settings of the connection you created will not be automatically updated if the data source settings are changed. This means you need to be careful about storing user names and passwords, especially if you change settings between integrated Windows security and database login in the DSN.

Best practices when using ODBC data connections

Moving apps with ODBC data connections

If you move an app between Qlik Sense sites/Qlik Sense Desktop installations, data connections are included. If the app contains ODBC data connections, you need to make sure that the related ODBC data sources exist on the new deployment as well. The ODBC data sources need to be named and configured identically, and point to the same databases or files.

Connecting to non-ANSI encoded data files

If you are experiencing problems with non-ANSI encoded data files when using an ODBC data connection, you can try importing the data files with a folder connection, which supports more options for handling character codes.

Security aspects when connecting to file based ODBC data connections

ODBC data connections using file based drivers will expose the path to the connected data file in the connection string. The path can be exposed when the connection is edited, in the data selection dialog, or in certain SQL queries.

If this is a concern, it is recommended to connect to the data file using a folder data connection if it is possible.

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – let us know how we can improve!