Henric Cronström, Technical Product Advocate at Qlik looks at the differences and similarities.
Qlik Sense is not just a new release of QlikView. Instead it is something different. But there are still so many similarities between the two products, so I thought it would be appropriate to dedicate a blog post to differences and similarities between the two.
Basically, the two products are two different user interfaces to the same analysis engine. This means that old scripts and old formulae will (almost) always work exactly the same way as before. (There are some smaller differences in that Qlik Sense uses libraries, and cannot always use relative paths for files.)
Hence, the two products both have the same Green-White-Gray logic; both use the same calculation engine; both have roughly the same response times; and you should use the same considerations for both when it comes to data modelling. This also means that many of the previous posts here on the Design Blog are just as relevant for Qlik Sense as for QlikView.
But the two products are still very different. And just as a parent cannot say that one child is better than the other, I cannot say that one product is better than the other. They are good at different things:
Finally, it is important to acknowledge that a piece of software is never ready. It evolves constantly:
Qlik Sense today is only the first version of something that will evolve further and get more features and functions as time goes on. Some of the features and functions of QlikView have not yet been implemented in Qlik Sense – there just hasn’t been time enough – but many of them will be implemented in coming versions.
Also QlikView is not yet a “final product”. The product will be developed further, and most likely we will see some of the new functionality from Qlik Sense also in coming versions of QlikView. The goal is to use the same platform for both user interfaces.
With these two tools, we believe that we are well prepared for the future.
The original blog post, published 29th July 2014 can be found here.
Moving on from Sage Line 50 to Sage 200 was the most logical option for us. As a company we were already familiar with Sage and CPiO’s ability to work with our bespoke database provider gave us the assurance we needed. We had found the right partner to make the change with.
CPiO’s ability to offer a one stop shop for software and hardware support was very appealing. The consultants demonstrated a good understanding of the solution and explained the purchase and […]
The transition to Sage ERP 1000 v4 has been very smooth, with very little or no disruption to the users.