https://community.esri.com/t5/data-management-ideas/quot-add-incrementing-id-field-quot-tool-should/idi-p/931551 <P>Currently, when you use the&nbsp;<A href="https://pro.arcgis.com/en/pro-app/tool-reference/data-management/add-incrementing-id-field.htm" target="_blank">Add Incrementing ID Field</A> geoprocessing tool to add an OBJECTID field to a non-geodatabase maintained spatial table, the associated unique index created by the tool ends up in whatever the database sees as the default tablespace. At least in PostgreSQL that I am using, I see the index ending up in the <STRONG>pg_default</STRONG> tablespace.</P><P>&nbsp;</P><P>It would be useful to be able to optionally specify the tablespace where the index will be created, so as to be able to avoid the use of the default tablespace.</P> Tue, 04 Oct 2022 18:24:36 GMT MarcoBoeringa 2022-10-04T18:24:36Z https://community.esri.com/t5/data-management-ideas/quot-add-incrementing-id-field-quot-tool-should/idi-p/931551 <P>Currently, when you use the&nbsp;<A href="https://pro.arcgis.com/en/pro-app/tool-reference/data-management/add-incrementing-id-field.htm" target="_blank">Add Incrementing ID Field</A> geoprocessing tool to add an OBJECTID field to a non-geodatabase maintained spatial table, the associated unique index created by the tool ends up in whatever the database sees as the default tablespace. At least in PostgreSQL that I am using, I see the index ending up in the <STRONG>pg_default</STRONG> tablespace.</P><P>&nbsp;</P><P>It would be useful to be able to optionally specify the tablespace where the index will be created, so as to be able to avoid the use of the default tablespace.</P> Tue, 04 Oct 2022 18:24:36 GMT https://community.esri.com/t5/data-management-ideas/quot-add-incrementing-id-field-quot-tool-should/idi-p/931551 MarcoBoeringa 2022-10-04T18:24:36Z