Skip to main content

Defining the connection parameters

This section describes how to add Snowflake as a data warehouse in a Qlik Compose project.

  1. Open your project and click Manage in the bottom left of the Databases panel.

    The Manage Databases window opens.

  2. Click the New toolbar button or click the Add new database link in the middle of the window.

    The New Data Warehouse dialog box opens.

  3. From the Type drop-down list, select the desired data warehouse.
  1. Enter the information as described below.

    • Connection input mode: Select Standard or Advanced.

      If you selected Standard connection input mode, specify the following:

      • Server Name: The URL for accessing Snowflake on AWS or Snowflake on Microsoft Azure.
      • Port: The port through which Snowflake will be accessed (default 443).
      • Authentication method: Choose Username and password or Key pair.
      • Private key: If you selected Key pair authentication, paste the private key file content into this field.

      • User Name: The user name for accessing the Snowflake database. The specified user must have read/write privileges on the Snowflake database.
      • Private key password: If you selected Key pair authentication and the private key file content is encrypted, specify the private key file password in this field.

      • Password: If you selected Username and password authentication, specify the password for accessing the Snowflake database.

      If you selected Advanced connection input mode, specify the following:

      • Authentication method: Choose Username and password or Key pair.
      • Password: If you selected Username and password authentication, enter the password for accessing the Snowflake database.

      • Private key: If you selected Key pair authentication, paste the private key file content into this field.

      • User name: If you selected Key pair authentication, specify the user name for accessing the Snowflake database. The specified user must have read/write privileges on the Snowflake database.
      • Private key password: If you selected Key pair authentication and the private key file content is encrypted, specify the private key file password in this field.

      • ODBC Connection String: The string of parameters required to connect to the Snowflake ODBC Driver.
      • JDBC Connection String: The string of parameters required to connect to the Snowflake JDBC Driver.
      • Warning noteCompose will concatenate the warehouse name to the ODBC/JDBC connection string.
        Information noteYou can connect to Snowflake with ODBC, using a proxy server and entering the appropriate ODBC environment parameters. For details, see ODBC Configuration and Connection Parameters - Snowflake Documentation.
        Information note

        You can connect to Snowflake with JDBC, using a proxy server and entering the appropriate JDBC connection string:

        jdbc:snowflake://<Snowflake server URL>:443/?&user=<snowflake user name>&warehouse=<Snowflake Warehouse name>&useProxy=true&proxyHost=<Proxy server name>&proxyPort=<Proxy server listening port>&proxyUser=<proxy server user name>&proxyPassword=<proxy server user's password>

    • Warehouse Properties: Specify the following:
      • Warehouse Name: The name of your Snowflake warehouse.

        Warning note

        "Warehouse" refers to the Snowflake warehouse and should not be confused with the data warehouse created by Compose.

      • Database Name: The database in which to create the data warehouse tables.
      • Data Warehouse Schema: The schema in which to create the data warehouse tables.
      • Data Mart Schema: The schema in which to create the data mart.
  2. Click Test Connection to verify that Compose is able to establish a connection with the specified data warehouse.
  3. Click OK to save your settings.

    The database is added to the list on the left side of the Manage Databases window.

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!