Select to view content in your preferred language

Allow exceptions to standardized query rules

941
2
05-30-2017 03:31 PM
Status: Open
stevegourley
Frequent Contributor

ArcGIS Server standardized SQL queries 

Allow standardize queries setting per service - not server 

These ideas have been open since 2013 and have not received any attention. If moving the standardized query setting to the service level is not something esri is interested in allowing then we need to make the standardized query rules customizable. 

Limitations of standardized queries
Standardized queries are applied to the entire ArcGIS Server site; they cannot be enabled for some services and disabled for others.
Standardized queries are not supported on joins between different workspaces. Additionally, database tables accessed through an OLE DB connection file are not supported. If your service data contains these sources, you'll need to use alternative methods for referencing your data.
Subqueries as a where clause, for example, POP_2010 = (SELECT min(POP_2010) FROM counties are not supported.

I think subqueries and database functions are a good option to start with since I would assume they are the most common reason to turn off standardized queries. Having a checkbox list of database functions to allow would be very helpful. And for subqueries an allowable template or a white list of queries is an option if it is not overly complicated. 

It is really problematic to disable standardized queries because one service needs to use a subquery or function. 

2 Comments
geonexusjames

sub-selects are a priority. especially with new association rules in UN, leveraging sub-selects would be very powerful.

SCS_ANST

Hi. This is still a pain point. As i've seen in the docu of ArcGis Enterprise 11, it is still only possible on site level to configure standardized queries. 

Is there a roadmap to support a customization of this "feature" on service level? Or at least to except some service from it?