Skip to main content
Announcements
Qlik Connect 2024! Seize endless possibilities! LEARN MORE
cancel
Showing results for 
Search instead for 
Did you mean: 
Not applicable

Direct Discovery

Hello All ,

      Need understanding on Direct Discovery, what is it ? how we can use it ? with examples.

1 Solution

Accepted Solutions
ToniKautto
Employee
Employee

rohit sharma please notice that Direct Discovery had a major rebuild in 11.20 SR5. This means that the syntax and implementation is not directly compatible between 11.20 SR3 and SR5 (or later). For Direct Discovery feature evaluation it is highly recommended that you do this in 11.20 SR5 or later.

In short the Direct Discovery feature is aimed for big data collections, that does not fit into memory during load. Instead QlikView queries data from the database based on users current selections. 

If your production environment is short on memory it is recommended that you evaluate if an increased memory will solve your deployment needs, instead of using Direct Discovery. The simple reason for this is that Direct Discovery loads data during application usage, and thereby adds latency to the user experience. The Direct Discovery performance will be in line with database side processing of the SQL queries and the data transfer time from database to QlikView. Direct Discovery will always be slower that evaluating data that has been loaded into memory during load.

View solution in original post

14 Replies
ashfaq_haseeb
Champion III
Champion III

Hi,

If you wana try for direct discovery, I would suggest you to try this out with V11.2 sr5 as it has many enhancement.

I'm sure below links will help you to start with.

http://community.qlik.com/docs/DOC-5534

http://community.qlik.com/docs/DOC-3781

http://community.qlik.com/docs/DOC-3710

http://community.qlik.com/blogs/qlikviewdesignblog/2012/11/08/qlikview-112-and-direct-discovery

Hope it helps

Regards

ASHFAQ

tresesco
MVP
MVP

Not applicable
Author

Thank you Ashfaq, could you please give some examples on how to use direct discovery in V11.2 sr3, i dont have sr5, demo app would be great.

Not applicable
Author

thanks tresesco, do you have any demo app for 11.2 SR3?

ToniKautto
Employee
Employee

rohit sharma please notice that Direct Discovery had a major rebuild in 11.20 SR5. This means that the syntax and implementation is not directly compatible between 11.20 SR3 and SR5 (or later). For Direct Discovery feature evaluation it is highly recommended that you do this in 11.20 SR5 or later.

In short the Direct Discovery feature is aimed for big data collections, that does not fit into memory during load. Instead QlikView queries data from the database based on users current selections. 

If your production environment is short on memory it is recommended that you evaluate if an increased memory will solve your deployment needs, instead of using Direct Discovery. The simple reason for this is that Direct Discovery loads data during application usage, and thereby adds latency to the user experience. The Direct Discovery performance will be in line with database side processing of the SQL queries and the data transfer time from database to QlikView. Direct Discovery will always be slower that evaluating data that has been loaded into memory during load.

Not applicable
Author

Hello toni, I have seen examples on direct discovery, in all of them they have used tables from DATABASE ,can't we load data from exel file or qvd's and use direct discovery on data extracted from these files?

ToniKautto
Employee
Employee

That is correct, it requires a SQL compliant database. The reason for this is that the feature targets big data quantities, larger than would fit in memory using the generic QlikView loads.

Content from files like Excel or text files simply can not become large enough to not fit into a modern computer memory. Once your data becomes to large for handle or store on file, you will also very likely move to storing it into a database.

QVD files stores data in the same format as QlikView stores it in memory. This means that QVD files are intended fro optimized loads, as they can be copied directly into memory. For this reason QVD files are assumed to fit into memory, and will also not be relevant for Direct Discovery. You are not able to store the QVD file unless the data fits into memory first so that it then can be written to file.

Not applicable
Author

thank you toni, could you provide some more examples or demo app for more understanding...

ToniKautto
Employee
Employee

The best way to evaluate Direct Discovery is that you install 11.20 SR5 on a test environment, and evaluate the feature after studying the Technical addendum and FAQ. Especially focus on the limitation of the feature, as this will set a clear boundary of what you can accomplish with the current edition of Direct Discovery.

QlikView Direct Discovery FAQ 11.2_SR5.pdf

QlikView 11 2 SR5 Direct Discovery Technical Addendum.pdf

If you do not currently have a database to test with, see the Demo below which will work easily with the Microsoft Adventure Works database, The first sheet in the application has shortcuts to the sample database file and to SQL Server 2012 Express, of which both are free of charge.

Direct Discovery_Demo_Adworks_11.2_SR5.qvw

The three items above should give you a complete walk through of the feature and capability of Direct Discovery. However, if all your current data fits into memory I would recommend continuing with regular loads and skip Direct Discovery for now.