Skip to main content
Announcements
Qlik Connect 2024! Seize endless possibilities! LEARN MORE
QlikProductUpdates

Extend your analytics capabilities with cloud databases using Direct Query!  Qlik is excited to announce the release of Direct Query, a new capability that allows applications in Qlik Sense SaaS to directly query cloud databases using SQL pushdown as users interact with data through visualizations and user filtering.

 

Differing from our industry leading analytics engine, Direct Query generates SQL queries on the fly against the source and executes the query and compute at the database level. From big data to near real time use cases, Direct Query empowers users of any level to easily explore and analyze the most recent data right from the database, increasing the speed to insight and decision-making. 

Direct Query complements our best-in-class analytics engine and extends the range of consumption techniques for analyzing data from cloud databases. The first connector rolling out for Direct Query will be for Snowflake with Databricks next on the roadmap and others planned, so stay tuned.  

Can't see this video? - View it on the Qlik Video Page - Direct Query Part 1 - Overview and Operation

Can't see this video? - View it on the Qlik Video Page - Direct Query Part 2 - Building Hybrid Analytic Solutions

How does Direct Query work?  

Direct Query can be activated at the database connection level. So, using Snowflake as the example, when building a new application and starting with a data connection, you will have the option to use Direct Query versus our analytics engine.  

The user can then select certain components of the source database –in the Snowflake connector users will see the options for role, database, and schema. Authentication for Direct Query is governed at the database level so users will only have access to what is granted from the source database. 

The user can then select a single view or multiple tables with the option of choosing the type of relationship between the data sets like full outer join or inner join.  

Once the relation is designated, an import live statement is inserted into the script in the load editor on the back-end and the visualizations can begin being built on the front-end. Since this is a SQL pushdown tool, users will need to use the function library of the underlying database. As of this blog, we will support the major 5 aggregations of sum, avg, min, max, and count. Also, some simple forms of set analysis will be available for filtering within measures of charts. 

After the charts and objects have been built, users can filter and interact with data in real time as Direct Query generates SQL on the fly and pushes the query and compute down to the source database. Keep in mind that every selection or filter within the app from a user, results in a query pushed down to the database and compute. 

Direct Query will also feature a seamless transition into our analytics engine for advanced interactivity and the full suite of capabilities. Check out Part 2 ‘Building Hybrid Solutions’ from the videos below.  

To learn more, check out these two videos on Direct Query: 

Part 1: Overview and Operation 

Part 2: Building Hybrid Analytics Solutions with On Demand App Generation (ODAG) 

 

To learn more about how Qlik and Snowflake together can optimize your investment into data and analytics, read our corporate blog here 

Join us for the webinar series, Do More with Qlik, on August 24th where our very talented Mike Tarallo will be showcasing Direct Query for Snowflake.  

22 Comments
agigliotti
Partner - Champion
Partner - Champion

Hi,
I guess I made a mistake, now all selections have been applied in the generated on-demand app.
But I still facing the issue in the Summary/Selection app when I apply the selections related to the generated app, look at the image below:

agigliotti_0-1663687007475.png

Did anybody face it?
Thanks in advance for your time.
Best Regards

1,020 Views
DavidFosterVF
Creator
Creator

When will this be available for cloud data warehouses other than Snowflake, BigQuery and Databricks?

0 Likes
938 Views
paulcalvet
Partner - Specialist
Partner - Specialist

Hello @QlikProductUpdates 

I try it but I have this problem.

In direct query, I create relationship because the name 

In my table retailers, I have the fields id, name and country

paulcalvet_1-1674482126873.png

In the table review, I have the field retailer_id

paulcalvet_2-1674482259155.png

I create a relationship to map this two fields :

paulcalvet_3-1674482343789.png

Qlik rename the fields to create the relation :

paulcalvet_4-1674482419237.png

But when I add it, it says that it can't add a field with a dot 😲😥 and I have this error when I add renamed fields in the application :

paulcalvet_5-1674482439366.png

 

 

 

896 Views
paulcalvet
Partner - Specialist
Partner - Specialist

If I change the order of the table in the relationship, it doesn't rename the fields...

885 Views
QlikAren
Employee
Employee

Thanks for letting us now @paulcalvet!
We have managed to reproduce the dot-issue now, and are looking into how to correct it.
We will let you know once it has been corrected.

829 Views
QlikAren
Employee
Employee

@paulcalvet We have solved the issue and we are about the deliver it. So within 2 weeks it will work for you.

776 Views
Shrankhla1195
Partner - Contributor II
Partner - Contributor II

@AlexOmetis is Direct Query available for on premise (Enterprise version) or only on SaaS?

 

682 Views
dsc
Employee
Employee

Hi @AlexOmetis

 It is SaaS only I'm afraid.

663 Views
paulcalvet
Partner - Specialist
Partner - Specialist

Hello,

The pivot table is not available for direct query !

This basic chart should be present like in all other BI tools 

@QlikProductUpdates  is it planned in the roadmap ?

 

Vote for this idea 😎

https://ideation.qlik.com/app/#/case/324570?currentProductId=9da99bc1-0dfb-4471-8e12-d23685578c43

 

415 Views
jtu363
Contributor
Contributor

Is direct query now available for Azure Databricks?

245 Views