I have several query layers in an ArcGIS Pro 1.4 project, each accessing the same database view, but each with a different where-clause in their source SQL-select statement. Each layer has thus only a few dozens or thousands of features, while the view itself in its entirety has millions of rows. Of course, no layer ever queries the entire view.
We distribute this ArcGIS Pro project to our users on a read-only file share.
- Could it be that ArcGIS Pro, in a rare circumstance that I have never observed so far, decides to call a the select-statement WITHOUT its where-clause?That would result in a very, very long-executing query that would put unneeded load on our DB-server, render the map in ArcGIS Pro unusable for dozens of minutes at least and clog the client computer's CPU and memory.
- Or does ArcGIS Pro guarantee to always use the where-clause?
Thanks in advance for your time & thoughts