Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Have anyone experience with going from Qlik to Microsoft BI, like SSIS, SSAS and SSRS. In that world they talk a lot about "cubes", I have not met that in Qlik so far, what would it be in Qlik language? I found some videos on youtube, but I cannot figure out what should be the revolutionary difference.
In the end I guess you need the basic understanding of databases and some kind of SQL, the rest is just different faces? Or are the systems radical different? What are the main difficulties switching to Microsoft?
Technically, a QlikView chart is a cube. A cube, with all the limitations of a cube, e.g. you cannot have too many dimensions, because then it becomes too slow.
But there, the similarities end. The systems are radically different.
Microsoft BI is an add-on on top of SQL Server 2014 and with it you can manage cubes. But it is not like in QlikView: In QlikView where you make a selection and it affects all charts, i.e. you are really not very limited by the fact that a cube only can have a few dimensions, since you can use several cubes simultaneously. Instead, you are more limited, since cubes normally don't interact with each other. You normally see one cube - one chart - and that's it.
You will never get the flexibility and user adoption with a classical cube tool. But then again - I am biased: I work for Qlik...
HIC
Technically, a QlikView chart is a cube. A cube, with all the limitations of a cube, e.g. you cannot have too many dimensions, because then it becomes too slow.
But there, the similarities end. The systems are radically different.
Microsoft BI is an add-on on top of SQL Server 2014 and with it you can manage cubes. But it is not like in QlikView: In QlikView where you make a selection and it affects all charts, i.e. you are really not very limited by the fact that a cube only can have a few dimensions, since you can use several cubes simultaneously. Instead, you are more limited, since cubes normally don't interact with each other. You normally see one cube - one chart - and that's it.
You will never get the flexibility and user adoption with a classical cube tool. But then again - I am biased: I work for Qlik...
HIC
Hi Mikael,
I have the experience but it's other way round. I have worked on MSBI stack for 3+ years before moving into QlikView. Every bit what HIC mentioned above is absolutely right. If you use QlikView for a week or two you would never go back to cubes. Again, I have to admit that I'm big Qlik fan and my views are biased as well.
You can find some video tutorials on my blog:
www.QlikShare.com
Good luck!
Cheers,
DV
Thx, I think it will be hard to get fully unbiased replies in this forum 🙂
What about the programming languages, sometimes it is SQL or QlikView is pretty much SQL syntax like?
-Mikael- wrote:
Thx, I think it will be hard to get fully unbiased replies in this forum 🙂
Opinions might be biased but not the experience. My personal experience - likes of MSBI & Cognos which use the cube technology is far away from QlikView. They've their own purpose for sure.
Yes, QlikView syntax is similar to ANSI SQL. It's advantage if you already know SQL and can think of SET instead of Rows.
Cheers,
DV
www.QlikShare.com