Skip to main content

Defining landing areas

In a Compose for Data Warehouses project, you can define any number of landing areas. Defining multiple landing areas is necessary if the data that you eventually want to be available in your data mart(s) is located in several different landing areas.

Before you can define a landing area in Qlik Compose for Data Warehouses, you first need to define a data warehouse.

For more information on adding data warehouses, see Setting up a data warehouse connection .

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

    The Manage Databases dialog box opens.

  2. Click the New toolbar button.

    The New Data Source dialog box opens.

  3. Provide the following information:

    Data source fields

    Field

    Description

    Content Type

    Choose whether the content in the landing area is Full Load, Change Processing or Full Load and Change Processing (according to the Qlik Replicate task definition).

    See also After applying changes below.

    Designated By

    Select whether the landing area is a Database or a Schema. This should reflect the target endpoint settings in the Qlik Replicate task.

    When Oracle is the Data Warehouse, this field is read-only since the Oracle landing area is always designated by Schema.

    For more information, see Defining a Qlik Replicate task.

    Database Name

    This field is not applicable when Oracle is the Data Warehouse.

    If the landing area is designated by a Database, specify the database name. This must be the same as the target database defined in the Qlik Replicate task.

    When Microsoft Azure Synapse Analytics is the data warehouse, the landing area database must be the same as the database defined for the data warehouse, although it should use a different schema.

    For more information, see Defining a Qlik Replicate task.

    Schema Name

    If a schema name was specified in the Qlik Replicate task settings, specify the same schema name here.

    When Oracle is the Data Warehouse, this must be the same as the schema defined in the Oracle target connection string in the Qlik Replicate task.

    For more information, see Defining a Qlik Replicate task.

    Error Mart Schema Name

    Specify the schema where you want the data mart exception tables to be created. Data that is rejected by data quality rules will be copied to tables in the specified schema.

    For more information on error marts, see Defining and managing data quality rules.

    After applying changes

    If you selected Change Processing or Full Load and Change Processing as the Content Type, you can determine whether the Change Tables will be deleted or archived after the changes have been applied (to the data warehouse tables). If you select Archive the Change Tables, you also need to specify a Database name and Schema name in the designated fields.

    Associate with Replicate Task

    Select this to associate your Compose for Data Warehouses project with the related Replicate task. Replicate tasks replicate the relevant tables from the source database to the landing area in your data warehouse. Specifying the Replicate task name will enable you to monitor and control that task from within Compose for Data Warehouses. However, before you can specify a Replicate task name, you first need to define the connection settings to the Qlik Replicate Server machine.

    To do this, click the Replicate Server Settings link below the Associate with Replicate task field and then configure the settings as described in Monitoring and controlling Qlik Replicate tasks.

  1. If you want to generate the model by discovering the source database in the Replicate task, leave the New Data Source window open for now as you will need to define connectivity to the source database in the Replicate task.

    For instructions on how to do this, see Defining Replicate data source connections.

    Otherwise, click OK to save your settings.