I was looking at Periscopedata and Chartio - it looks like they support SQL for visualization. Looked pretty impressive, at least on demo level, especially Periscope stuff.
As I understand, the approach of "traditional" BI tools is to focus on UI (drag-and-drop) or internal scripting (Qlik, DAX, etc.), but it would be cool to see SQL support in visualizations in Qliksense...
normaly you can use all SQL statements within Script-Area, and they do normaly work,
to your issue:"The reason is that sometimes I am completely lost with set analysis grammar.";look at this, i am sure that helps you: (uveren pomoshet tebe)
i hope that helps
As with any language you need to learn syntax and it will not be a problem in the future to understand what you are writing. I know Set Analysis can be scry sometimes.
Writing SQL on UI is not possible in Qlik Sense as it does not support this language in expressions.
You can load data with this query and then in QlikSense use sum(Sales) expression. Obviously then you loose bunch of information - sales with Volume < 200.
As an alternative you can concatenate this querry to original dataset.
No you can't you will need to learn set analysis just as you learnt sql
Once you learn something it becomes easier to work with
There are lots of content around set analysis on the community
And this wizard if it helps you
Thanks for your responses.
I was not asking for resources to learn the set analysis or advice "that you need to learn something".
I'm quite comfortable with set analysis, but I'm not a full-time QS developer to invest my time into all possible details and depths on syntax/grammar of it.
I was just asking for possibility to use SQL in visualization _together_ or _instead of_ set analysis syntax - that's it.
For example, Omar's response is a good hit on my answer.
Yes, it was.
And it was the most helpful response so far, even it describes the limits of SQL usage in QS.
My line of thinking is that SQL is de-facto query language, it is everywhere and it is humanly readable, even years after you've developed something. There are several systems on the market which use sql to create visualization, in a very efficient manner.
Why not enable to do this in Sense?
Because it would be a waste of time writing nested sql statements
Not all expressions will be as straightforward as a simple sum (sales)
Try imagining to recreate the functionality of firstsortedvalue () using SQL!
Even microsoft has MDX and DAX,similarly Set Analysis simplifies things
You feel sql is easy because you know it , once you learn something everything becomes easy.
Why not? Because in my opinion it would be a step back for Qlik.
If other tools with SQL based visualisations are efficient, why dont we hear about them among market leaders? I guess it is because such a solution is not flexible. I agree that it is possible though!
Now to more important thing. Implementing SQL script in QS expressions is impossible due to how associative Qlik engine works. If you would have done SQL on UI you would loose all associative benefit from Qlik product which is its very stron part.
You also very clearly stated that you think of SQL as of querry language and I agree with you. Qlik Sense front end is not querry. It is whole, integrated datamodel. To make it working consisten you need to either apply SQL querry on all objects - which ultimetly means querry on whole datamodel which then can also be done on back-end.
I would give it another think-go.
On the other hand on script level i prefer to use SQL and i do it, mainly because it deals a lot faster with statements like "Where "and especialy "Group by". Still - end result needs to be full data model.
1. I have never seen in the plans of developers use in the visualizations of the language SQL. Now this is not and it is unlikely to be in future. Discussion of this topic does not make sense - it is unlikely that the developer will change the concept of the system for the sake of convenience of several users.
2. Practice has shown that the possibility of using the language SQL directly in scripts very much depends on the developers of drivers SQL (different drivers support a different set of supported commands and functions). In my opinion, that the data must be directly collected in Qlik (well, it can be imposed restrictions on the amount of data, if necessary). Further all processing should be carried out by means of Qlik. This is just my personal opinion, no more.