I have 8M geometry in SQL and I’m sure spatial geometry exists for the table.
We know the issue is when you in primary levels and ThinkGeo find the intersection of the features with the CurrentExtent, so it should load all of the features, I mean 8M…
The one thing that came to my mind to load the features, is to load some part of them using WhereClause in SQLServerFeatureSource. So I change the WhereCaluse based on ZoomLevel.
But at this point, I cannot get to the performance that I expect, Do you have any idea to improve my implementation?
I measure the query time, it takes on average 8 seconds for each tile, and we have 4 tiles in CurrentExtent that contain features.
I think the GetFeatures and Drawing both are executed in the same thread.