Is a Qlik QVD DWH still a thing?

[Noctis]

Currently, we're using a Data Vault strategy on Snowflake with Datavaultbuilder, but in my opinion inefficiently. Out of the Data Vault we generate Dimension and Fact tables for analysis and store them as QVDs. These QVDs undergo additional transformations to meet the distinct requirements of various dashboards.

Because we use the ETL Process in Snowflake and in Qlik Itself, I thought for myself "Cant we just do everything in Qlik?"

Opinions are much appreciated!!!

[Noctis]

Push

[chriscammers · Accepted solution]

In my opinion if you are transforming the data from your fact and dimension tables in Qlik then I would recommend moving all those transformations to the snowflake side. This would help you prevent inconsistencies between different Qlik Apps. You are probably correct that you can definitely decide where you want to do all the transformations that are happening in Qlik so in the end it is entirely up to you. As for Qlik Data Warehousing I have clients who do everything in Qlik and it is no problem.

[marksouzacosta · Accepted solution]

This is a great topic to debate. Most of our customers do everything in Qlik because it is usually faster and easier to do ETLs in Qlik than other regular Databases. However, everything remains locked in Qlik. But now that Qlik supports Parquet files, things are getting more interesting on this subject.

Disregarding advanced Qlik platform features and tools such as Talend, I personally prefer to keep everything on the Database side for some reasons: 

1. We keep everything centralized in one place, including security rules and management
2. It is way easier to integrate with other BI tools, Development Platforms, APIs, share data, etc.
3. Will be easier to move to other database platforms

At the end everything depends on implementation size, existing platforms, company culture and preferences.