Qlik Fix: How to Reload a Single Table in Qlik Compose

[Troy_Raney]

This video is part of the Qlik Fix Video series. If you found this video useful, check out the other Qlik Fix Videos.

Environment

• Qlik Compose

This video demonstrates how to reload a single table in Qlik Compose without having to reload ALL of the tables in a Data Warehouse

Here is a link to more information in the Support Knowledge Base

Transcript

Hi and Welcome to Qlik Fix

This video will demonstrate how to reload a single table in Qlik Compose,

Without having to reload ALL of the tables in a Data Warehouse task.

This can be done with both Data Warehouse AND Data Lake projects,

but this demo will be using a Data Warehouse project.

In this project, the data mart is built.

Click on the Source Database connection,

A Qlik Replicate Task is set as the source,

With the task name: SQL_Server_TO_SF.

This means that the Replicate Landing table is the source to our Qlik Compose task.

Test the connection – that’s successful.

In Qlik Replicate, we can see the details of that task.

This is a Microsoft SQL to Snowflake Full Load and Change Data Capture task.

So, the Snowflake on Azure endpoint is actually the Source for the Compose task.

The database name is EYD_LZ.

Back in Qlik Compose, you can see the same landing Database name, EYD_LZ.

To reload only the Order Details table,

Switch to Monitor mode,

If you highlight a specific table, it gives you the option to reload only that table.

However, if you go to Qlik Compose,

This is the Full Load task

And this is the Change Data Capture or CDC (Change Processing) task, and the option to reload only one table isn’t available.

Begin, by stopping the Replicate Task that is the source of the Compose task.

We can see the last time the Full Load was completed.

Stop the task.

Back in Qlik Compose, click on Manage, the Data Warehouse

To verify that we’re getting any recent changes or updates in Qlik Compose, we will run a CDC task once to capture those latest changes.

So, with CDC highlighted, click on Run the Change Data Capture task.

In this example there are no updates, but those would have been shown here.

The next step, is to go back to the Warehouse task, highlight the Full Load task, and Duplicate this task.

Give it a clear name. I will give it the same name, _DUP

Change the Task Type from the default to Full Load Only.

Highlight this new task, and since we only want to reload One table, uncheck the table we don’t want to reload, and select Handle Duplicates.

This is because we don’t want Compose to completely reload all the data from Replicate. We only want to capture the data that is missing.

When running the task, Qlik Compose will compare and only bring over the updates that are missing.

Now click on Generate.

Now that those instructions have been generated, back to Replicate,

Highlight only the table that we’re interested in, and click on Reload.

This will wait until we run the task, so click on the drop-down menu of the Run button, and select Resume Processing.

The task has started again, and Order Detail table will update with a new Loaded time here.

So, Replicate did a reload for one specific table, Order Details in this case.

Back in Compose, on the Landing_DUP,

Since the instructions have already been generated, click on Run to start the task

This is a one-time activity, only brining the missing changes to that specific table in Compose.

The missing updates would be listed here.

Now the data is in-sync in the Data Warehouse table.

Now that this is complete, to clean things up, go back into Data Warehouse management,

Highlight the _DUP task and delete it.

Select both of these options, and delete.

You can now continue to run normal CDC.

I hope this helps.

Thanks for watching.

(music)

Nailed it!

@Nanda_Ravindra