Why do we have the �??move edits to base�?� option,

1386
4
02-01-2013 05:15 AM
Highlighted
Honored Contributor
Why do we have the �??move edits to base�?� option,

I�??m wondering for which purposes the option of �??move edits to base�?� is offered! With this option, users are losing functions such as �??enable archiving�?�, for example.

[ATTACH=CONFIG]21313[/ATTACH]

Then in which cases this option (move edits to base) is useful?

Thank you

Best

Jamal
4 Replies
Highlighted
Frequent Contributor II
Jamal,

When data is registered as versioned with the option to move edits to base, edits are automatically moved from the delta tables to the base tables when you save edits to sde.default or when you post edits in a child version to sde.default.

Saving edits in a child version of default does not cause edits to be moved from the delta tables to the base table.

This option is really designed to support nonversioned edits by third-party applications.

There is a good flow diagram here that helps you decide if that option would work with your workflow:

http://resources.arcgis.com/en/help/main/10.1/index.html#//003n000000t0000000

Regards

Anthony
Highlighted
Regular Contributor III
Jamal,

As the ESRI WEBHELP clearly describes: " Checking this option causes edits that have been saved to the DEFAULT version, whether edited directly or merged from other versions, to be saved in the base (business) tables. Edits to other versions remain in the delta tables when you save.

This option is available for simple features only�??those that do not participate in a topology, network dataset, or geometric network. Therefore, if you open the Register As Versioned dialog box and find the move edits to base tables check box is unavailable, it means your dataset contains a topology, network dataset, or geometric network.

Regards,
Highlighted
Honored Contributor
Jamal,

As the ESRI WEBHELP clearly describes: " Checking this option causes edits that have been saved to the DEFAULT version, whether edited directly or merged from other versions, to be saved in the base (business) tables. Edits to other versions remain in the delta tables when you save.

This option is available for simple features only�??those that do not participate in a topology, network dataset, or geometric network. Therefore, if you open the Register As Versioned dialog box and find the move edits to base tables check box is unavailable, it means your dataset contains a topology, network dataset, or geometric network.

Regards,



Thank you Anthony and Asrujit for the very useful answer.

1. Till now I couldn�??t figure out the justification for the use of the �??move edits to base�?� option. Why the user should do care about whether the edits are transferred DIRECTLY to the base table or not? What are the consequences?

2. If the �??move edits to base�?� is covered (function wise) by the �??NON-move edits to base�?� option, then why anyone should choose the �??move edits to base�?� option? Do anyone love to lose functions in this case?

3. By choosing �??move edits to base�?� one will be missing many functions (disadvantages):

a) Archiving
b) Topologies/network/geometric/fabric

4. What might be disadvantages of using the �??NON-move edits to base�?� option all the time?


Best

Jamal
Reply
0 Kudos
Highlighted
MVP Regular Contributor

Registering the data as versioned without the option to move edits to the base table is beneficial because the other option does not allow for conflict detection, nor replication.

See this:
http://desktop.arcgis.com/en/arcmap/10.4/manage-data/geodatabases/data-maintenance-strategies.htm

Reply
0 Kudos