nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Default Sorting for SDE Feature Class

mvolz47

To All ArcSDE Users:

I have a feature class in SDE that I open up and see that the records are not sorted by the ObjectID field in ArcCatalog. I thought this was the default field that ArcCatalog uses to sort SDE records when a feature class table is first opened in ArcCatalog.

What would cause an SDE feature class table not to be sorted by ObjectID by default?

Additional information: This feature class has records appended to it from a join between another SDE feature class and a table in SQL Server 2005 that have common fields that are used for the join. These records are appended on a daily basis.

Trouver plus de publications taguées avec

Accepted answers

All comments

LalitArora

Thanks Vince for prompt reply.

I'm not deleting table. GP Script user is not the owner of the table. So it can not create or delete schema. I'm just deleting existing features and inserting new one in exiting schema.

DeleteFeatures_management - deleting rows

arcpy.da.insertcursor - inserting rows

If I use CopyFeatures, FeatureClassToFeatureClass, Append management tools, output features show up correctly sorted on ObjectID. I can't use these tools in present case.(limitation in my scenario)

If same feature data set (i.e. same spatial extent) show up differently created by above two ways.

What's missing to show it up correctly?

VinceAngelo

Once you start using DELETE, the database is well within rights to place rows in any page it deems appropriate (each table has its own "high water mark" of previously allocated extents).

If you actually TRUNCATE the table instead of DELETE, then the rows would likely be placed in the order you inserted them (since the high water mark is cleared, and new blocks are being allocated)

It's important to know that the database is not obligated to return rows in any particular order unless an ORDER BY clause is used. Also, once the spatial extent reaches a quarter of the overall extent, spatial queries are likely to return features in spatial index order.

- V

LalitArora

Hi Vince

I found this post mostly matching to my issue. I'm using ArcGIS Version 10.2.2.

In my GP script, I deleted all old features from a FC using arcpy.DeleteFeatures_management.

and Inserted new features by using arcpy.da.insertcursor, record inserted in the correct order, I can see from auto generated object ids.

But on opening attribute table in ArcMAP or preview in ArcCatelog the table don't show records sorted on Object ID. I tried to rebuild indexes, set spatial index on FC using owner. It did not help

If I use CopyFeatures, FeatureClassToFeatureClass, Append management tools, features show up correctly sorted on ObjectID. In my GP scenario I'm not the owner of dataset/feature class. I'm working with another user having privilege to insert update delete records.

What's the difference. How I can see data on sorted order?

Thanks and Regards

Lalit Arora

VinceAngelo

As a rule, ArcSDE clients like ArcGIS do not specify an ORDER BY clause, which is
the only way to enforce a sort order on any column. ORDER BY is an expensive
option which forces extra intermediate passes through the result set.

The registered rowid column (usually OBJECTID) is only required to be NOT NULL and
unique. The population rules sometimes cause gaps or counterintuitive sequencing in
a simple "SELECT * FROM table" query, but spatial constraints will generate the
appearance of that as well.

- V

Rejoindre la conversation

Les membres connectés peuvent publier, suivre les mises à jour, et plus encore. Nouveau ici ? Inscrivez-vous gratuitement.

Liens rapides

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.