With a properly tiered setup and governance that's a non-issue. Qlik Cloud has lineage nowadays too, so even a spaghetti architecture can be unraveled relatively easily.
I'm not sure if that's a precise comparison. QVD's, if I understand, are a cached copy of the data. So it's more like stacking materialized views. So you have storage issues as well.
The main point is that, if you don't know what you're doing, any tool will let you build a spaghetti architecture. That's not something that's inherent to Qlik.
We're currently migrating a pretty large enterprise client from Qlik to Power BI. We've been keeping a list of differences, pros and cons with the goal of writing a balanced post.
I'd love to see it! I may try to put something together from the little I've learned, but it won't be very comprehensive since I don't work with Qlik professionally.
Pre-pandemic, I made reports in an old Qlikview version that I still can't create in PowerBI. Old fashioned, bizarre at times, but a lot better than the half baked visual layer in PowerBI.
I mean, I suspect you could switch Qlikview with SSRS in that sentence and it would hold true as well. Qlikview had a very 00s aesthetic as far as tools go (when I tried it 6 or years ago)
Qlik isn't bad-bad, but it's a bit of a mess with different non-integrsted solutions as @joeydantoni.com mentioned.
I would say it's better than PBI in some areas, worse in others.
The perfect BI-tool simply does not exist.
Qlik blows. The Qlik zealots on reddit will double down but that supposed robust user community is non-existent. I left my first BI job because we couldn’t kill Qlik as an organization.
Similar but couldn’t find anything. I think I even posted on the Business Intelligence subreddit and nobody had anything. (I’m the one that posted the PBI Reddit thread about the excel file issue with refreshes that you replied to!)
There really needs to be. When my last org moved from Tableau and OBIEE to Power BI, some consulting company even had a free webinar that was a couple hours called “Power BI for Tableau Developers” and it was the most helpful thing I’d found. When I started my current role, I looked for something
It's all good. I'm in the middle of a week-long workshop I'm providing and the audience is looking to move from Qlik to Power BI over the next 2 years. I've got enough to get by for this week.
I guess if we are being specific, this customer is migrating away from Qlik Sense.
But yeah it would be kind of like if a company were to put a cloud based interactive reporting service, a cloud based paginated reporting service and on-prem versions all under the same moniker.
Comments
I do think it's easier in Qlik to create something quite pretty. But the operational and fixing of Qlik reports is so much shittier.
QVD farms.
Global variables.
Associative engine.
Don’t ask me why I know these things… I won’t confirm that I used Qlik in a past life as a contractor.
With that said, all BI-tools benefit from hood data models. Regardless of what the marketing material tells you.
But to be fair I think you can create this kind of mess in many BI-tools.
I would say it's better than PBI in some areas, worse in others.
The perfect BI-tool simply does not exist.
Me, when the economy people opens a CSV in Excel and saves it (in another format) and sends it to me:
I use PBI today, but evaluated a number of on-prem BI tools a few years ago, I might remember some details, but not all of them.
But yeah it would be kind of like if a company were to put a cloud based interactive reporting service, a cloud based paginated reporting service and on-prem versions all under the same moniker.
Wait a minute......
The users will have to learn a new tool and some like change and some don't, so important to keep them on board. 👍