Qlikview 9 product roadmap

Posted by William on 10/02/2009 under News | 5 Comments to Read

As you might know, QlikView 9 will be out in May or June this year. In my daily news check I found this interesting article:

While reading this article, the following parts caught my attention.

• The vendor had previously announced support for warehouse applications supplied by Sybase IQ and Kalido.

So what does support for warehouse applications mean when we talk about Qlikview and who are Sybase IQ and Kalido?

A quick look at their websites (here and here ) returns the following key words:

• handle business change
• consistent information
• business model-driven approach
• prototype, iterate and deploy
• dramatically faster results
• low cost
• Speed and flexibility

Sounds like the well known marketing terms of Qliktech right )? I can’t speak for the products from my own experience (feel free to comment about your experiences!), but when we just look at those words it seems a right fit. But these are only some terms. More interesting is the question why Qliktech wants to support those datawarehouse apps while they claim to be a substitute. I think this is quite a clear signal that the need for a dwh is there in many situations (tracking history, integration, data cleaning / profiling, enrichment). It’s smart to collaborate. Where other BI vendors deliver complete solutions for the whole BI spectrum, Qlikview as a product does not.

• “A strategy called ‘QlickView everywhere’ will make it easier to do mash-ups and portals,”

The term mash-up refers to a new breed of Web-based applications created by hackers and programmers (typically on a volunteer basis) to mix at least two different services from disparate, and even competing, Web sites. A mash-up, for example, could overlay traffic data from one source on the Internet over maps from Yahoo, Microsoft, Google or any content provider. In other words: Google maps (and much more) integration at last !

Combining this with simple, nice and smooth portal integration sounds like a keen strategy. Portal software (Sharepoint, Liferay etc) is getting more common every day. Ultimate goal is a personalized user portal displaying custom made information. The Right Information to the Right Person at the Right Time. With that said, it’s clear that there is a link between portal software and data analysis (the right information).

Beautiful times will come for Qlikview customers and developers. I’m sure about that! Please feel free to comment about the points I discussed! What do you think about the support of datawarehousing and what do you know about Kalido and Sybase IQ?

Share and Enjoy:

Mike S said,

Kalido is already offering .QVW as an available output format in its Dynamic Information Warehouse product. I have played with it, and it could certainly be improved (it doesn’t even work with 8.5 yet), but it is only in its infancy and has some interesting potential.
Gilles said,

Hi Mike,
Can you explain a bit more about the output format? How does that work? What does it deliver, how does it look? What’s in the output?
Mike S said,

The default output QVW has no front end except for a few Kalido logos and background. The generated script has a simple calendar table, the main table (one SQL select run against a Kalido table via a database connection), and the output of the main table stored as a QVD.

You can change the front end of the output QVW in whatever way you like, run the refresh in Kalido, and the underlying data will be updated without undoing your changes to the front end. However, the script always resets to the default that was generated by Kalido, meaning that creating a truly customized application would probably mean using the QVD it generates as a data source for a separaate QVW would make more sense.

I’m optimistic at how it could eventually work. At this point, it’s so new, it’s scarcely documented, so take what I say with a grain of salt. It was mostly result of trial and error, just playing around with it and testing a few scenarios.
QlikView 9: Export Layout to XML said,

[...] Kalido is exporting basic QVWs and QVDs,? That feature required custom code integration. Soon any one of us can achieve the same end result: export a complete XML specification, import the XML into QlikView, and hit reload to execute the script. If QlikTech can make this happen from the command-line then the entire process can be hidden and the end user receives a freshly baked QVW (or QVD!). [...]
Kalido, Qlikview and Netezza | Quick - Qlear - Qool said,

[...] Information Appliance which you can read following this link. In an earlier post on this blog about the roadmap for Qlikview 9 we noticed a support for Kalido announcement. And now it’s there. Kalido already had support [...]