Hi, Only a workaround till MS fix the bug (I hope). But after reading the second post in this thread http://social.msdn.microsoft.com/Forums/en/sqlspatial/thread/1d7c3d89-c9bf-4338-869b-a9d563a81838 I added a not very selective index to a GEOGRAPHY table and now SDE benefits from the Spatial Index. By adding a definition query such as for eg. WHERE PERENNIAL IN ('1','2','3') - Perennial being a field in a table of hundreds of thousands of records with an index that has only 3 categories (not very selective) the SQL Server Query Optimiser has decided that the Spatial Index is lesser cost than the current clustered index scan and rendering via SDE is now order of magnitudes faster at lesser scales. Not ideal but till the bug's fixed it will have to do...
... View more