Adding field to Versioned Enterprise Geodatabase

[chadhickman]

I have run into some problems in the past and I just want to verify the steps to properly 'unversion' my Enterprise Geodatabase in order to add a new field in multiple feature classes:

1. Reconcile all versions

2. Delete versions except for the default

3. Unversion database

Could someone please verify these are the necessary steps so I can avoid any complications?

Thanks,

Chad

[Robert_LeClair · Accepted solution]

Chad - the data owner of a versioned feature class can add a new field without going through the whole process of unregistering and re-registering.  Once the data owner creates the new field, it is seen in all versions. 

Regards,

Robert LeClair

Esri-Denver

[chadh]

I have found that not to be true. I have done that before and it "ruins" the whole database

[Robert_LeClair]

By "ruins" the whole database, what do you mean?  Since there's only 1 feature class (that is versioned), adding an attribute field would be seen across all versions.