enterprise geodatabase - Versioned to unversioned: How to undo edits in an edit session on an unregistered table

I'm considering switching some of my tables in an Oracle enterprise geodatabase from versioned to unversioned.

The pros of having unversioned tables would be:

But of course, there are a few cons:

• 
  

  Users can't create and edit named versions. This isn't a huge problem for me, because my organization ultimately doesn't use versioning technology properly anyway. We don't really do long-transaction editing, which is what versioning is intended for. Instead, we just do short transactions on the default version (without creating separate versions).

  
  


• 
  

  It's only possible to edit either registered or unregistered tables in an edit session. Not both. So users have to stop editing and switch between edit modes to edit one kind of data or the other.

  
  


• 
  
  

  It's not possible to undo or redo edits in an edit session on unregistered tables.

  
  

This last one is a potential deal breaker. It's really quite infuriating to not be able to undo an edit in an edit session. Sure, the user can stop editing, and not save the changes, but then they lose all the unsaved edits in that edit session.

Is there a way to undo/redo edits on unregistered tables in ArcGIS Desktop?

Answer

I often wonder if someone has tried the following.

(This response will probably show how much I don't know about where ESRI's technology have moved to in the past 5 years.)

1. Leave the Enterprise GeoDatabase as a plain-vanilla short transaction DB.



2. Create a File GeoDatabase. Smart editing tools are available including undo/redo.


3. Extract the data to be edited into the File GeoDatabase and do all ones editing in it: create versions, throw away etc.


4. When merging final version back to DB, check for differences, resolve in FGDB and then do final commit.

Enterprise DB is protected from specific user scenarios, long transactions, and presents current state to all business applications. All other non-ESRI apps can see the current state. The only issue is if two people edit same business objects but I wonder how much this occurs and whether it is sufficiently common to cause problems. If so, just edit versioned Enterprise GeoDatabase.