Multi-Versioned Views - Updgade from 10.0 to 10.1

[MeleKoneya]

We are going to upgrade our SQLServer SDE databases to 10.1    I understand that in 10.1,  the mult-versioned view is now called a versioned view and that it is created when a database is versioned in 10.1 and not only by command line as in 10.0

I also understand that we can create the new versioned views on a versioned database if they don't exist using 10.1 utilties, but if  we already have them in a 10.0 SDE database, do we need to recreate them after migrating or will the existing multi-versioned views function as before?

Thanks,

Mele

[VinceAngelo]

I'm not sure if you need to, but I would recommend that you do so.

- V

[MeleKoneya]

Vince,

I was looking at a multi-version view in our development database that was updated to 10.1 and did not see any issues.   

We are using the multi-version views to read data from using this query type

exec pvm.sde.set_current_version 'pvm.web_edits'
select * from pvm.pvm.FACILITIES_MVW


Is there some functionality in 10.1 that would be available if we delete the existing multi-version view and recreated it?


Thanks

Mele

[EmadAl-Mousa]

i think the current multiversion views in your 10.0 version will still be valid (you will not see them in your catalog tree in ArcCatalog 10.1) they can be viewed in the properties of the "versioned feature class" associated with it.

in 10.1 the new multiversion views has a standard naming of featureclass_vw , created automatically when version a feature class not to base table. you don't have control over the naming of the multiversion view as before (in 10,9.3,..etc) with the command line.

[VinceAngelo · Accepted solution]

For standardization, mostly, I guess (all the things I thought were new at 10.1 seem
to have been at least introduced at 10.0).

- V

[MeleKoneya]

Vince,

Thanks for clarifying this issue.    We may update the multi-version views down the road, but it sounds like it is not an immediate concern as they are working.

Mele