Skip to main content

I'd love to see a parameter on the writer feature types of the Esri Geodatabase Writers where you have an option to create or update the Spatial Indexes for the Esri Geodatabase feature types.

It would be a great feature to update/rebuild spatial index on the feature types after they have finished loading. This would make your data ready to go after a big data loading job has completed. Then you wouldn't have to rely on some custom Python hack to update you spatial indexes.

The writers I see can benefit from this feature are:

  • Esri Geodatabase (GEODATABASE_SDE)
  • Esri Legacy ArcSDE (SDE30)
  • Esri Geodatabase (File Geodb API)
  • Esri Geodatabase (File Geodb ArcObjects)

Hi!

This would greatly improve the usability and convenience of using the ESRI geodatabase writer.

Regards,

Joe Hansson

 


Agrees that it would simplify a lot!


Please add the option to update/rebuild spatial index in a ESRI GDB!


The current work around is using a python script with arcpy management tools. It also looks like you could potentially use a sql statement to rebuild them.


I am using pythonCaller with both AddSpatialIndex_management and RebuildIndexes_management to create spatial index extent for feature classes under a MS Sql Server spatial database but it seems it is not working as expected, nothing happens.

Anyone had this issue?

Any workaround?


Bump for this, it would be tidy if it's practical to achieve this with the writer rather than looking at python scripts. Perhaps it could remove the index at the start of writing, write features then re-add the index and maybe even auto-calculate based on feature sizes?


Were very interested in this


Totally. When you truncate / append the whole table every day to keep the data up to date, you have to rebuild the indexes somehow.


Page quoted has been removed from Esri support and does not appear to be maintained any more. It was Article ID: 000006051 "FAQ: How can ArcSDE performance be improved?" for oracle 8/9/10 or SQL Server 200/2005, and is available from archive.org circa 2017/2018.

 

I won't repost here but it involved running SQL as the SYS or SA/dbo user on either dba_indexes or using dbcc dbreindex. I believe this is no longer an Esri approved method for administering indexes any more (Our DBA would not allow us to do this, so it is moot.) and has moved to Python/GPT.

 

example: Rebuild system table indexes (ArcGIS Pro latest)

 

Failing an in-Workspace feature, we're using arcpy either separately in batch (custom task/application) or as part of the workspace scripting shutdown python parameter: Question: Update spatial index