topic Best practices (data warehouse+Qlik) in Connectivity & Data Prep

Best practices (data warehouse+Qlik)

kshangaun — Mon, 17 Apr 2023 09:09:27 GMT

Hi,

I’m a BA for the Data Warehouse and the Qlik Apps for our company. I just recently switched companies and at my new company, they try to solve almost everything with Qlik Apps, but in all my classes and/or certificate programs I was taught that the front end tool should be ‘dumb’. The data logic should be in the data warehouse. The consultants for Qlik think otherwise and try to transform in qvd. What is the best practice in your company?

Re: Best practices (data warehouse+Qlik)

mshann01 — Wed, 26 Apr 2023 20:52:42 GMT

@kshangaun I've been working as a Qlik developer and T-SQL developer both for the past 10 years. I've always leveraged extracting and transforming as much of the data in our data warehouse as possible. As a team lead and manager, I've also preached this as the best practice. Many teams are not lucky enough to have production access to the data warehouse or the knowledge to perform complex extractions and transformations at that layer. But if you do have that expertise, I encourage you to use it. It will allow you to pivot and reuse your data marts and warehouses for other BI tools if your company or other teams use them. We utilize SSRS so having access to the same data marts and tables is a huge benefit. Otherwise, you'd have to recreate the logic of the qvd layers in all of your other tools. And if your company unfortunately switched to another BI product (hopefully they don't) then you save yourself time from having to recreate the qvd logic. If your company goes "all in" on Qlik and you can leverage qlik marts extensively across your organization with the qlik data catalog, then it likely doesn't matter where you perform the transformations.