topic Executing non-SELECT queries is disabled. But it's a CTE... ? in Connectivity & Data Prep

Executing non-SELECT queries is disabled. But it's a CTE... ?

110 — Tue, 19 Jul 2022 16:33:42 GMT

I can understand delete / insert / truncate etc. being disabled by default, but why would CTE's be blocked?

Without unwinding the query into a horrible windowed select statement, is there an easy work-around without enabling non-select queries ( I.E. Actual dangerous queries like Delete/ Insert etc. )

Re: Executing non-SELECT queries is disabled. But it's a CTE... ?

Or — Wed, 20 Jul 2022 07:35:16 GMT

What we do is pop the CTE query into a view and have Qlik run a standard Select from that view.

Re: Executing non-SELECT queries is disabled. But it's a CTE... ?

110 — Wed, 20 Jul 2022 08:49:00 GMT

Thanks @Or - that's what I'd normally do, however I don't have sufficient rights on the SQL server to create views either so I'm in a catch 22. 😛

Re: Executing non-SELECT queries is disabled. But it's a CTE... ?

Or — Wed, 20 Jul 2022 09:15:28 GMT

Assuming you can't get someone to create the view for you, sounds like you'd need to either enable non-select queries, or re-do the logic, then. Depending on what it is exactly, it might be easier to pull the query without the WITH block, pull the WITH block individually into a separate Qlik table, and then join them in Qlik rather than on the database side.