Hello,
We have recently upgraded our ArcMap instances to 10.4 and are now having performance issues with our SQL Spatial Views.
Querying on the database side is fine, its when the views are loaded into ArcMap 10.4 when the slowness starts. If I fiddle with the view I can make it perform better but its hit and miss. The 10.4 client is doing something because in 10.3 clients the views perform as expected.
Our SDE Geodatabase has also been upgraded to 10.4 and is running on SQL Server 2012 (64 bit)
One additional note: If I create the exact same view as a "Query Layer" in ArcMap the data performs as expected. Its only when its compiled as a SQLSpatial View when the slowness starts.
Has anyone else had this problem or have a solution?
Drew
Query Layers and registered spatial views are very different creatures. The registered views know the expected geometry type and expected data envelope due to metadata stored in the sde.sde_layers table. This allows the Direct Connect DLL to avoid using a spatial query constraint if it would be inefficient (e.g., it wouldn't significantly reduce the number of features).
You've also had some significant trauma to your database due to the various upgrades. Rebuilding all the indexes and all the index statistics would be a good course of action at this point. If you have any large (250k+ row) tables that are performing poorly, you should consider spatially sorting them into a new table, and measuring for spatial query performance.
In the future, please use specific time intervals in performance questions (e.g "17.3 minutes"), and include the topology type (point/line/poly) and the number of rows involved.
- V