Export QlikView Entire Data model as SQL query to use in Power BI to build sample Power bi report to show demo.

[RajuS1]

Hi All,

As per my current project migration plan i have to migrate one complex report from QlikView report to PowerBi. But it has very complex Data model, So is there any option to export QlikView entire data Model as SQL Query.

[marcus_sommer · Accepted solution]

If you mean just the data you could store each table as csv and load them into Power BI. If you relates to all the script-parts which are creating the QlikView data-model - there is no translation into any language. This means you will need to translate and adapt each single part of your own - especially as the ETL capabilities and the performance from Power BI is quite limited. 

[Or]

Adding to Marcus's response, do note that a Qlik schema may not translate to other BI tools even if you export the data. Qlik is a lot more forgiving than most BI tools when it comes to how you set up your data schema in most regards, and a lot less forgiving in a handful of others (mostly on how tables are joined).

[RajuS1]

Hi Marcus,

Thanks for your quick response. do we need to store each table as one csv or total all tables as one csv.

[marcus_sommer]

Each table as single csv. But like @Or hinted it might not be enough just to load these data into Power BI because the relationship between them in the data-model is relational in Power BI and associative in QlikView.

So be careful whereby if it's the recommended star-scheme data-model it should work without much efforts. You will need them to create any sensible UI ...  

[robert99]

@RajuS1 

From my experience the loading of tables and linking them all together is not that different between PBI and Qlik, PBI you load all the tables then link them by drag and drop. Not by common names as in Qlik. But PBI can be slower if there are too many associated tables (fact linked to a dimension linked to another dimension etc). Qlik seems to still work fine when many tables are all associated by field names.

PBI can do one thing that I wish Qlik could do. That is link one dimension table to one or more Fact tables. So no Canonical dates are needed. Also there isn't any need to set-up AsOfPeriod fields in script (rangesum above is quite limited) as PBI handles accumulations using DAX measures. 

But apart from the above (that really needs to be set-up well using Qlik script. Then it works fine) I much prefer Qlik Sense. I'm surprised that a company using QV would not convert to QS