Skip to main content Skip to complementary content

Install the Qlik ODBC Connector Package

The Qlik ODBC Connector Package must be installed manually for QlikView. For Qlik Sense, the ODBC Connector Package is installed automatically and does not require separate installation. The connector can be excluded from the Qlik Sense installation if necessary.

Excluding the Qlik ODBC Connector Package from Qlik Sense installation

Warning noteIf any version of the Qlik ODBC Connector Package is installed on the system, it must be uninstalled before the current version can be installed.
Information noteIf you intend to use the Qlik ODBC Connector Package with QlikView on a system with Qlik Sense Desktop, you install it with the QlikOdbcConnectorPackage_setup.exe after you have installed Qlik Sense Desktop.

System requirements

The Qlik ODBC Connector Package only runs on systems with 64-bit processors. It can be installed on any 64-bit system that runs QlikView. For more information, see: System requirements for QlikView.

The Qlik ODBC Connector Package also requires Microsoft .NET Framework 4.8 or later.

The Qlik ODBC Connector Package runs with QlikView and is designed to work with the same web browsers as QlikView.

Installing the ODBC Connector Package

Do the following:

  1. Download the QlikOdbcConnectorPackage_setup.exe file from Product Downloads.

    Install connectors separately

  2. Stop the QlikView services, if they are running.

  3. Run the QlikOdbcConnectorPackage_setup.exe.

    The Qlik ODBC Connector Package installation wizard sets up the installation environment and completes the installation.

    The connectors in the ODBC Connector Package are then available from QlikView with the name of the databases to which they connect.

  4. Start the QlikView services again.

When you open the Edit Script dialog in QlikView, you can select ODBC Connector Package and then select a specific database connector on the ODBC Connection panel.

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!