Skip to main content Skip to complementary content

Loading data from databases

You can load data from commercial database systems into Qlik Sense using the following connectors:

  • Connectors specifically developed to load data directly from databases through licensed ODBC drivers, without the need for DSN connections. For more information, see Qlik Connectors: Database.

  • Connectors that use the Microsoft ODBC interface or OLE DB. To use Microsoft ODBC, you must install a driver to support your DBMS, and you must configure the database as an ODBC data source in the ODBC Data Source Administrator in Windows Control Panel.

Loading data from an ODBC database

There are two ways to load data from a database.

To connect directly to a database through one of the Qlik-licensed ODBC drivers, see the instructions for Database connectors on the Qlik Connectors help site.

For more information, see ODBC Connector Package.

Qlik-licensed ODBC drivers support the following databases:

  • Amazon Redshift
  • Apache Drill
  • Apache Hive
  • Apache Phoenix
  • Apache Spark
  • Azure SQL
  • Cloudera Impala
  • Google BigQuery
  • Microsoft SQL Server
  • MongoDB
  • MySQL Enterprise
  • Oracle
  • PostgreSQL
  • Presto
  • Sybase ASE
  • Teradata

To use the Microsoft ODBC interface, do the following:

  1. You need to have an ODBC data source for the database you want to access. This is configured in the ODBC Data Source Administrator in Windows Control Panel. If you do not have one already, you need to add it and configure it, for example pointing to a Microsoft Access database.
  2. Open the data load editor.
  3. Create an ODBC data connection, pointing to the ODBC connection mentioned in step 1.
  4. Click Data Selection on the data connection to open the data selection dialog.

Now you can select data from the database and insert the script code required to load the data.

Related learning:

Learn more

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!