Does spatial index make dataset work faster?

Are there any disadvantages in having it?

All datasets in my sde don't have a spatial index. I thought I should add it to make things faster

closed as too broad by PolyGeo Mar 14 '18 at 6:33

Please edit the question to limit it to a specific problem with enough detail to identify an adequate answer. Avoid asking multiple distinct questions at once. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.

  • Don't forget to take the Tour that describes our focused Q&A format. When you tested did you find that a spatial index made a dataset work faster? – PolyGeo Mar 14 '18 at 6:33
  • Depending on your database you may already have a spatial index, PostGIS, from what I remember, adds a spatial index by default. It would be interesting though to test/record your transactions prior to indexing and then again after indexing to see if a spatial index improved performance. – Michael Stimson Mar 14 '18 at 6:39

Yes, spatial indexes makes the spatial query faster. Check this: http://desktop.arcgis.com/en/arcmap/10.3/manage-data/geodatabases/an-overview-of-spatial-indexes-in-the-geodatabase.htm

  • However, it depends on the query. The speed is better if the query contains a spatial part that is selective enough. For example, if you select with a bounding box that covers all the data then spatial index makes things slightly slower (check the index and select everything vs. just select everything). – user30184 Mar 14 '18 at 9:21
  • Indexes will be of no use if the optimizer determines that the query requires a full table scan. The presence of indexes slows insert operations, but usually the cost is offset by indexed query speed. – Vince Mar 14 '18 at 10:34

Not the answer you're looking for? Browse other questions tagged or ask your own question.