Enforcing Unique Values in SDE

[aam]

Is there a way to enforce unique ID for a feature class in SDE when the user is adding new stuff to make sure the integrity of the data is not compromised.

I have editors who occasionally add new addresses into a feature class. There have been instances where duplicate addresses were entered. I am wondering if there is a way to enforce unique values.

[Bud]

You can add a unique index using the properties in Catalog. Composite unique indexes are also possible there too.

[aam]

Would this work in non versioned environment?

[Bud]

Yes.

[VinceAngelo]

Keep in mind that there has not been an "in SDE" since the rewrite at 3.0.  Data resides "in" a database. All of the tools of the supported databases are available, though some of them may be incompatible with successful deployment (e.g. 64-bit integer types).

The versioning  model can be incompatible with UNIQUE values, since multiple conditional edits can exist in the ADDs table, and enforcement would be delayed until much too late.  You need a proactive validation process that looks for eventual duplicates.

- V