Advantage of Yellowfin vs Qlikview!
2 May, 2014
Hi Every One ,
Actually we are a company that want to add a BI tolls for analysing and reporting .
We don't have any Idea of Yellowfin but we want to intagrate it .
What we want to know that wat's the advantages of yellowfin in relation to Qlikview??
Thanks for your respense
Actually we are a company that want to add a BI tolls for analysing and reporting .
We don't have any Idea of Yellowfin but we want to intagrate it .
What we want to know that wat's the advantages of yellowfin in relation to Qlikview??
Thanks for your respense
I worked 3 years with QlikView before to know Yellowfin. I think that the main differences are:
1- The amount of RAM memory necessary to the servers. I worked in a project with Qlikview that the server had 128Gb RAM and also other project with 512Gb RAM. In the Yellowfin server is not necessary this amount of memory to run the same amount the data. It is impossible to host a big project in SAAS model with QlikView because of the price to host a server with a lot of RAM memory.
2- You can not share the same Dimension in others projects with QlikView because all the Dimension or table from database goes to RAM memory again to each project. Ex. DimProducts goes to memory in a project about Sales and goes to a memory again in other project that use the DimProduct. In a ROLAP model used by Yellowfin you can share Dimensions (Conformed Dimensions).
3- To do ETL in QlikView is necessary to write a lot SQL commands scripts by hand. In advanced projects is necessary to learn the QlikView special scripts commands. In Yellowfin is not necessary to learn new SQL commands because is used the drag and drop wizard SQL or if you prefer you can write SQL using the SQL ansi and nothing more.
4- The user management, groups and roles in Yellowfin is much more powerfull and easy to use than Qlikview.
Arthur
1- The amount of RAM memory necessary to the servers. I worked in a project with Qlikview that the server had 128Gb RAM and also other project with 512Gb RAM. In the Yellowfin server is not necessary this amount of memory to run the same amount the data. It is impossible to host a big project in SAAS model with QlikView because of the price to host a server with a lot of RAM memory.
2- You can not share the same Dimension in others projects with QlikView because all the Dimension or table from database goes to RAM memory again to each project. Ex. DimProducts goes to memory in a project about Sales and goes to a memory again in other project that use the DimProduct. In a ROLAP model used by Yellowfin you can share Dimensions (Conformed Dimensions).
3- To do ETL in QlikView is necessary to write a lot SQL commands scripts by hand. In advanced projects is necessary to learn the QlikView special scripts commands. In Yellowfin is not necessary to learn new SQL commands because is used the drag and drop wizard SQL or if you prefer you can write SQL using the SQL ansi and nothing more.
4- The user management, groups and roles in Yellowfin is much more powerfull and easy to use than Qlikview.
Arthur
I want to add that the metadata management is also easier and much better to handle in Yellowfin, QV has a lot of IQD files. In Yellowfin is centralized in the server, no desktop tools needed and extremely easy to deploy on other servers.