Solved! Go to Solution.
Hi Jamal, versioned views used to be called multiversion views. Versioned views are automatically created for datasets that are registered as versioned using ArcGIS for Desktop 10.1 or higher. If you were using ArcGIS prior to 10.1, you would have needed to manually create the multiversion views using the ArcSDE command line tools. In your example, I see that some data registered as versioned have versioned views and some data do not based on your screenshots. Was this geodatabase upgraded from a pre-10.1 release?
Perhaps this article about Enabling SQL Access (for 10.2) will explain some possible reasons for what you're seeing...
Version views are also automatically created when you enable archiving on nonversioned datasets beginning with ArcGIS for Desktop 10.2. Additionally, there are situations when a version view will not exist:
For these situations, you can Enable SQL Access on those specific datasets from ArcGIS for Desktop. Could any of these be the possible cause in your case?
- You have tables or feature classes that were registered as versioned prior to ArcGIS 10.1 and did not manually create a versioned view using the sdetable �??o create_mv_view command.
- You registered a table or feature class as versioned using ArcGIS 10.1 or a later release, but you did not have the privileges necessary to create a view in the database.
- You enabled archiving on a nonversioned table or feature class, but you did not have the privileges necessary to create a view in the database.
- The version view was deleted mistakenly using SQL or database management system tools.
I tried this workflow in SQL Server Express 2008 R2 and in Oracle 11g R2 (220.127.116.11) using a 10.2 client:
- Create table called TEST
- Register table TEST as versioned, then enable Archiving
- Check in RDBMS to see if TEST_EVW was created
- Create feature class called TEST1
- Register feature class TEST1 as versioned, then enable Archiving
- Check in RDBMS to see if TEST1_EVW was created
In the case of SQL Server Express, I observed that step 3 did not show that a version view of the TEST table was created (either before or after Archiving was enabled). However, step 6 did yield a version view of the TEST1 feature class which got created upon registering it as versioned.
In the case of Oracle, I observed that both step 3 and step 6 yielded version views as expected based upon how Esri's documentation is written.
Therefore, I can only conclude that in SQL Server the automatic creation does not work for tables upon registration as versioned, but it does work for feature classes. This could potentially be a bug.
As far as I know, the way to create the version view manually is to use the Enable SQL Access tool when right clicking the object class. You might be able to extract the SQL for an existing version view, modify its contents to fit the object class you desire, and run it in SQL Server Studio Manager but I don't know what else under the hood might be required by ArcSDE. I think doing something like that would be at your own risk. 🙂
EDIT: You could also try the sdetable �??o create_mv_view command using the 10.2.x version of the ArcSDE command line tools. I'm not sure if it will create an _EVW or an _VW object though.