Geodatabase Multiversion View creationg control, naming, and Visibility in future releases

Idea created by mousaem on Jan 15, 2013
    New
    Score150
    Geodatbase multiversion views are based on feature class that is versioned to "not to base table". in ArcGIS version 10, the geodatabase administrator maintained more control in creating it.

    we used to use the command: sdetable -o create_mv_view

    now in ArcGIS 10.1 the following is being observed:

    1.multiversion views are automatically created when you register your feature class to "versioned not to base table", which should not be the case epsecially if i don't want one to be created.

    2.mulitversion views are not "displayed" in the ArcCatalog 10.1 tree, it can only be viewed through the properties of the feature class under "General" TAB.

    3.the new multiversion view created automatically by the system are named with system standard naming, Geodatabase administor has no control over naming the new multiversion view. I personally used to name my multiversion views in the system with "_MV" convention so that from database level i can distiguish it from normal Oracle Views.

    i recommend in future relases that the geodatabase administror have more control over the "creation", "naming", and lisitng the multiversion view in the catalog tree for ease of tracing. this can be part of the ArcGIS Desktop GUI interface administration (especially with SDE user connection).