versioned view creation - versioning not to base table

427
4
Jump to solution
04-15-2014 12:15 AM
EmadAl-Mousa
Occasional Contributor III
whenver i am attempting to version a feature class to "base table" a versioned view is automatically being created. which is strange since "versioned views" will be created when perform versioning NOT to base table.

i have attached a snap shot image of my feature class (name of the layer is scratched out for security reason).

My Environment:

ArcSDE Geodatabase 10.1
Oracle 11gR2 (11.2.0.3)
ArcGIS Desktop 10.2

0 Kudos
1 Solution

Accepted Solutions
George_Thompson
Esri Frequent Contributor
Hi Emad,

This is expected behavior. Versioned views are created in every feature class that is versioned by design. The below is an exerpt from the help documentation:

If you decide to register a feature dataset, stand-alone feature class, or table as versioned with the option to move edits to base, right-click it in the Catalog tree, point to Manage, then click Register As Versioned to open the Register As Versioned dialog box. Check Register the selected objects with the option to move edits to base. 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.


http://A quick tour of registering and unregistering data as versioned  -Under the section Registering as versioned with the option to move edits to base.

The underlined portion is the important section, if the edits are made to the DEFAULT version they will get pushed to the base table, but if they are made in other versions they remain in the delta tables.

What is a versioned view? -  http://resources.arcgis.com/en/help/main/10.2/index.html#/What_is_a_versioned_view/006z0000000q00000...

...Versioned views are automatically created for tables or feature classes that are registered as versioned in ArcGIS 10.1 or later releases.....


Hopefully this help!

George
--- George T.

View solution in original post

0 Kudos
4 Replies
George_Thompson
Esri Frequent Contributor
Hi Emad,

This is expected behavior. Versioned views are created in every feature class that is versioned by design. The below is an exerpt from the help documentation:

If you decide to register a feature dataset, stand-alone feature class, or table as versioned with the option to move edits to base, right-click it in the Catalog tree, point to Manage, then click Register As Versioned to open the Register As Versioned dialog box. Check Register the selected objects with the option to move edits to base. 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.


http://A quick tour of registering and unregistering data as versioned  -Under the section Registering as versioned with the option to move edits to base.

The underlined portion is the important section, if the edits are made to the DEFAULT version they will get pushed to the base table, but if they are made in other versions they remain in the delta tables.

What is a versioned view? -  http://resources.arcgis.com/en/help/main/10.2/index.html#/What_is_a_versioned_view/006z0000000q00000...

...Versioned views are automatically created for tables or feature classes that are registered as versioned in ArcGIS 10.1 or later releases.....


Hopefully this help!

George
--- George T.
0 Kudos
EmadAl-Mousa
Occasional Contributor III
Thanks George for your replay and clarification.


just one point that still is not clarified to me.......according to this link: http://resources.arcgis.com/en/help/main/10.2/index.html#/What_is_a_versioned_view/006z0000000q00000...


in the definition of the versioned view
: "When you query a versioned view, you can see the data in the base (business) table and the edits that are stored in the delta tables. The triggers used by the versioned views update the delta tables when you edit the versioned view using SQL."


This does not imply that versioned views are based on "versioning not to base table" ? since the definition is shwoing that this view can be used through "SQL" to edit both "base tables" & "delta tables".


Regards,
Emad
0 Kudos
AsrujitSengupta
Regular Contributor III
Emad,

Even if you are Registering your data as Versioned with "Move Edits to Base" option...the delta tables do play a role when the editing is done on any other version, other than the DEFAULT.

http://resources.arcgis.com/en/help/main/10.2/index.html#//003n000000rp000000

Under the heading "Registering as versioned with the option to move edits to base" its mentioned that:

If you decide to register a feature dataset, stand-alone feature class, or table as versioned with the option to move edits to base, right-click it in the Catalog tree, point to Manage, then click Register As Versioned to open the Register As Versioned dialog box. Check Register the selected objects with the option to move edits to base. 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 is why the Versioned Views are created when you Register data as Versioned with move edits to base option.
0 Kudos
EmadAl-Mousa
Occasional Contributor III
Ok, Thanks.
0 Kudos