[fdo-users] Can't select features using SQL Server data connection

[Jackie Ng]

To add to what Hans has said:

You *need* a primary key on your spatial table. Not only does this make your
spatial data selectable, it is also a pre-requisite for creating a spatial
index, which you also need.

Are you dealing with highly complex geometry data? Consider pre-computing a
Reduce()'d version of your geometry data and server that out at higher zoom
levels and serve the detailed version at lower zoom levels
(https://docs.microsoft.com/en-us/sql/t-sql/spatial-geometry/reduce-geometry-data-type?view=sql-server-2017)

In terms of diagnosing slow performance, it really helps to understand
execution plans. This topic ventures into DBA territory so not knowing what
an execution plan is saying would be understandable.

- Jackie



--
Sent from: http://osgeo-org.1560.x6.nabble.com/FDO-Users-f3898664.html