In the same category: compare in-memory solutions is this post by Boris Evelson as well: http://blogs.forrester.com/boris_evelson/10-09-01-not_all_in_memory_analytics_tools_are_created_equal where Boris gives advice on how to compare in-memory solutions. Nice read as well, and nice comments from two Qlikview adepts

There’s just one thing they always seem to forget at Qlikview: to have such a nice way of ” analysing and visualising all your data” you DO NEED a solidly build and well architectured datawarehouse!

Reading through the QlikView Docs I found the chapter about security, explaining an example how to implement it but unfortunately the QlikView Docs aren’t so clear and I had to search through the QlikView forum to find people with similar issues.

Issues I encountered :

1. Fetching users from the database within the section access does not work. After a succesfull reload I closed down the QlikView App and every user I tried to login with was denied access. So the QlikView apps did become useless, lucky me I made a backup.

2. Adding an inline table with admin users and concatenating a load statement with the users from the database did not work either (at least not the way I always write a concatenate statement). As mentioned in the the QlikView Docs all column names and values need to be in upper case if not they will be converted. But as experienced this is not the case, you need to explicitly make every column upper case with the function Upper().

Why I first insert an inline table is mainly because of fixed users that never change and secondly because of this post of William (link to post ).

Finally this is the code that works:

DbUsers_login:
LOAD
ID
,	LOGIN
,	TYPE
,	NAME;
SQL SELECT *
FROM "SEC"."USERS_LOGIN";

Section Access;
Star is *;

Security:
LOAD * INLINE [
ACCESS, USERID, PASSWORD, ROLE
ADMIN, ADMIN, 123, *
];

CONCATENATE (Security)
LOAD
'ADMIN' as ACCESS,
upper(LOGIN) as USERID,
'123' as PASSWORD,
'*' as ROLE
Resident DbUsers_login;

Section Application;

drop table DbUsers_login;

One thing really new to me was the following part and I quote:

The main ingredient of the performance secret sauce in QlikView is that selections are compiled straight into machine code. (QlikTech gave me the impression that this post is the first time that will be publicly revealed.) Notes on that include:

• In the old days, QlikTech thought compilation gave a 10X performance benefit vs. interpreted code. However, 5X might be a more up-to-date figure.
• It’s not just code; part of the compilation is to create temporary lookup tables.
• A single calculation can use multiple cores. QlikTech thinks it’s done a very solid job of engineering efficient multicore parallelism. (Note: So far as I could tell, Hakan was using “calculation” to refer both to queries and, well, calculations.)
• There’s a good reason QlikView runs only on Intel-compatible processors. A port would be painful.

So read the full story here: The underlying technology of QlikView

I consider this as a little bit strange partnership. I thought Human Inference works on your source systems, like your main CRM system and would love to hear how this works in conjunction with qlikview. Any thoughts?

User Enablement

List Box Expressions — add values, graphs to your list boxes to show data beyond simple frequency

Mekko Chart — a new native chart type that can add additional perspective to a standard bar chart

Metadata tagging — add comments and tags to the table and field you load into QlikView documents to enhance design time decisions

Container Objects — a new presentation object that allows you to create a group of related objects for review and use as a single entity.

Linked Objects — use standard object definitions within a document, allowing you to manage and maintain a consistent look and behavior for standard entities in one document

Associative Search — building on the existing QlikView search capability, review matches for strings across entities associated with the current list box

First User Experience — a streamlined, first time walk thru for any new user looking to understand key concepts of building their first QlikView from an Excel file

Enterprise Manageability

Building on from the enterprise deliverables with QlikView Server in QlikView 9.0, QlikView 10 unveils more centralized control around security and administration for all deployments. Features include:

Audit Logging — meet compliance requirements with logging options on who accesses which documents, navigates to which sheets in a document and performs which searches on which sheets

Consolidated User Management – A single point to manage the configuration of each user.

Section Access Management — builds on consolidated user management and delivers a single point of definition for access management. Allows all documents to reference a consistent security setup

Granular Collaboration Permissions — manage who can create collaboration objects, which type of object and against which documents.

*NEW* QlikView Extensions

As well as focusing on how QlikView can be integrated into other portals and viewpoints, in QlikView 10 we are bringing the outside world into QlikView. QlikView Extensions allow an implementation to embed externally defined visualizations inside a QlikView document. Maps, charts, graphs, HTML, Flash, Silverlight, can all now be rendered and interact with standard operations inside any QlikView 10 document. A simple interface permits a developer to expose the new object via standard property dialogs. Once included selections in list boxes will update the data in the new display, and if permitted allow for selections to be made on the new object to drive updates across the rest of the document.

Other new features:

QlikView Server APIs for management capabilities

New optimized data format for direct data loading into QlikView (QDS)

Multi-threaded loading of data

32 & 64 bit ODBC/OLE-DB independence providing 64 bit environments which need 32 bit drivers with a single framework to build applications.

• Beta1 is now available for internal use
• April 22 we will make Beta2 available for partners
• June 9 we will make a Release Candidate (RC) available to partners and customers
• October 6 QlikView 10 will be GA.

Our goal is to provide a significant amount of time for QlikView to be in the hands of our employees, partners, and customers prior to going GA.  This will allow everyone to contribute to testing real life usage, validating new features, and learning about the new capabilities before we launch the new version.  QlikView 9 had 11 weeks of beta period, QlikView 10 has 29 weeks.  We will be providing lots of training materials and opportunities for everyone to provide feedback, so please take responsibility to do so.

Official press release here: Qlikview for iPad sets new standard for tablet-based, interactive business intelligence

Product story here: Qlikview for iPad

Demonstration video: Qlikview for iPad (special thanks to QVapps)

Qliktech registered for IPO. Official press release is here, first thoughts are here and here by the QVapps blog, and an article in the Seattle times. Qliktech is looking to raise a $100 million dollar to pay of some debts ($7 mio) and the rest is for “general corporate purposes”.

There is this announcement that qliktech will largely drop its support for their java client in version 10 that will be generally available in October 2010 (let me guess: 10-10-10?). They will focus on their AJAX client.

First beta release of version 10 is out, we are trying to get into the qv10 beta program to keep you updated!

Regards,
Gilles

Highlighting in Notepad++: http://guerrillabi.com/syntax_highlighting_qlikview with thanks to Guerrilla Business Intelligence