OBJECTID - configuring auto increment via SQL Server post feature class creation

[AnnetteFarrell]

We have a SQL Server SDE asset data warehouse that is filled without involving ArcGIS technology. 
The data warehouse is used with AGE 11.1 and Pro 3 and these feature classes are used in a read only non versioned manner.

The ETL tooling used to fill the data warehouse has no way of handling the auto increment on the OBJECTID.

The data warehouse developers have proposed turning auto increment on for the OBJECTID field in SQL Server via a script AFTER the feature class has been created in ArcGIS Pro.

What is the wider impact of doing this when the feature class table will be read only and non versioned?  The feature classes are simple tables with assets and have no attachments.  I've had a look at this post already but the wider impact is not fully clear to me.

Thanks  

[ShannonShields]

Annette,

when tables or feature classes are part of a SQL Server geodatabase and created via ArcGIS then the ObjectID values are managed/generated by two stored procedures and a table that allow for IDs to be generated in larger blocks, and also manage multiple simultaneous users adding features. There is a stored procedure sde.next_rowid() (or dbo.next_rowid) that takes a geodatabase table/feature class as input and returns the next value for the ObjectID field. It uses the related stored procedures and ID table so IDs do not get reused and the sequence of subsequent IDs is preserved. That might be an option for the ETL operation.

But, do these tables need to be registered with the geodatabase? You can still interact with them in a read-only capacity without them having to be registered. Then you are free to manage a unique identifier field however you want - you can make the ObjectID an Identity field and have it auto-increment that way.

-Shannon