Is it possible to use the Identity property within SQL Server for a feature class?
Is this to be a simple feature class with a native geometry type, or registered with the geodatabase and versioned?
- V
Is there a certain criteria where it would work and where it wouldn't? For a typical feature class, registered with the geodatabase, versioned or non-versioned (if versioned, I'm assuming it'd need to be on the A table if it would work).
I'm really just after a good way of assigning an auto-incremented field in the table that is NOT the OBJECTID.
"Possible" and "supported" are different standards. You can sometimes get away with some unsupported types if they look close enough to supported types, but only if you don't press the issue too strongly. Identity columns are not supported in versioned geodatabases.
I can't be the only person after an auto-incremented field within the database. Is there a way of doing this within SSMS with a trigger, stored procedure, etc...?
Signed in members can post, follow updates, and more. New here? Register a free account.
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.
