What limitations do I get, when I chose to register as versioned with the option to move edits to base?
Answer
There are tradeoffs. I don't use this option because it limits the ability to create "check-out replicas" (show stopper for me). Another limitation when you chose this option is that you can't edit feature classes that participate in a topology.
Many people use this option because they need to support third party (non-ESRI) applications. When edits are made to the DEFAULT version that is registered with the option of 'move edits to base', those edits are immediately moved to the base tables rather than being stored in delta tables and requiring a sync operation... This is usually the only way that a third party application can interact with a versioned geodatabase.
No comments:
Post a Comment