This is how I've done it in the past. Not sure how long the command line sdelayer will be around though.
In SQL Server:
CREATE TABLE myFC (
ID INT IDENTITY(1,1) NOT NULL PRIMARY KEY,
SHAPE Geometry -- Could be a Geography
CREATE SPATIAL INDEX myFC_sdx ON myFC (SHAPE) -- Make your own spatial index
BOUNDING_BOX =(0, 0, 100000, 100000) --Use some sensible bounds
,GRIDS=(HIGH, HIGH, MEDIUM, MEDIUM)
From a command line:
sdelayer -o register -l myFC,SHAPE -C ID,USER ... connection information, etc
Note: When you export this to another geodatabase these IDs will not increment there. I am assuming that you are talking more about publishing rather than distributed editing though.
This will not work with Feature Classes registered as versioned.