Skip to main content
Announcements
Global Transformation Awards! Applications are now open. Submit Entry
cancel
Showing results for 
Search instead for 
Did you mean: 
110
Creator
Creator

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

 

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.  )

 

 

 

 

Labels (1)
3 Replies
Or
MVP
MVP

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

110
Creator
Creator
Author

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.  😛

 

 

Or
MVP
MVP

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.