topic Re: �??Version view�?� for tables\layers, in Data Management Questions

???Version view??? for tables\layers,

Anonymous User — Tue, 08 Apr 2014 09:49:24 GMT

Original User: Jamal432@gmail.com

???Version view??? for tables\layers,

I couldn???t figure out how particular tables\layers are given the ???Version view??? property while others don???t have it

For example, in the screenshot below, the ???project??? table has this property

[ATTACH=CONFIG]32904[/ATTACH], [ATTACH=CONFIG]32905[/ATTACH]

In return, the ???companies??? table doesn???t have it.

[ATTACH=CONFIG]32906[/ATTACH], [ATTACH=CONFIG]32907[/ATTACH]

Form where this property (versions view) is set?

Thank you

Best

Jamal

Re: �??Version view�?� for tables\layers,

WilliamCraft — Tue, 08 Apr 2014 10:01:15 GMT

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?

Re: �??Version view�?� for tables\layers,

Anonymous User — Tue, 08 Apr 2014 10:25:27 GMT

Original User: Jamal432@gmail.com

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?

Thanks William.

This is what confusing me the most. I�??m using ArcGIS 10.2.

As I create new table and this table is registered as version then the version view is not AUTOMATICALLY created

Scenario (ArcGIS 10.2):

�?� the �??H�?� table is create in the Q.mdf database.

[ATTACH=CONFIG]32908[/ATTACH]

�?� This table is registered as version.

[ATTACH=CONFIG]32909[/ATTACH]

�?� Nevertheless, the version view is NOT automatically created

[ATTACH=CONFIG]32910[/ATTACH]

What might be the issue here?

Re: �??Version view�?� for tables\layers,

WilliamCraft — Tue, 08 Apr 2014 10:57:26 GMT

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:

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.

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?

Re: �??Version view�?� for tables\layers,

Anonymous User — Tue, 08 Apr 2014 13:36:56 GMT

Original User: Jamal432@gmail.com

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:

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.
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?

Thank you very much William for the prompt help,

None of the cases that you have provided can be applied to my issue.

Could you please try it in your database? In case you create a table in the SQL enterprise database, does the version view is created automatically?

I tried to do the same on the ArcGIS 10.2.1 but fails to create �??versions view�?�. In the screenshot below, I have created the �??k�?� table using the ArcGIS 10.2.1 and everything is enabled, nevertheless, the version view is not created.

[ATTACH=CONFIG]32913[/ATTACH], [ATTACH=CONFIG]32914[/ATTACH]

Which tools\settings can be used to automatically create �??version view�?� for a particular table\layer?

Re: �??Version view�?� for tables\layers,

WilliamCraft — Tue, 08 Apr 2014 14:21:27 GMT

I tried this workflow in SQL Server Express 2012 and in Oracle 11g R2 (11.2.0.2) using a 10.2 client:

Create table called TEST

Check in RDBMS to see if TEST_EVW was created

Create feature class called TEST1

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.

Re: �??Version view�?� for tables\layers,

Anonymous User — Tue, 08 Apr 2014 15:12:31 GMT

Original User: Jamal432@gmail.com

I tried this workflow in SQL Server Express 2008 R2 and in Oracle 11g R2 (11.2.0.2) 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.

Thanks William,

I�??m not sure if ESRI experts may join this thread to have their feedback regarding this issue. What is strange is that this issue still appears even in 10.2.1

By the way, is there a way to enable this version view from the �??SQL Server Management Studio�?�?

[ATTACH=CONFIG]32921[/ATTACH]

Re: �??Version view�?� for tables\layers,

Anonymous User — Tue, 08 Apr 2014 15:19:47 GMT

Original User: crafty762

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.

Re: �??Version view�?� for tables\layers,

Anonymous User — Tue, 08 Apr 2014 15:40:56 GMT

Original User: Jamal432@gmail.com

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.

Very much appreciated William

I couldn�??t find the �??Enable SQL Access�?� tool neither by clicking the table\layer from the ArcGIS Desktop not from the SQL Server Management Studio�?�?

[ATTACH=CONFIG]32923[/ATTACH], [ATTACH=CONFIG]32924[/ATTACH]

How to approach this command?

Re: �??Version view�?� for tables\layers,

WilliamCraft — Tue, 08 Apr 2014 15:42:49 GMT

The Enable SQL Access command shows up in the first screenshot of the two you just recently posted. It appears in the 10.2+ versions of ArcGIS for Desktop.

Re: �??Version view�?� for tables\layers,

Anonymous User — Tue, 08 Apr 2014 16:07:37 GMT

Original User: asrujit

I tested this on an Oracle 11.1.0.6 sde 10.2 geodatabase, but was able to reproduce the same behaviour as in SQL Server for Tables.

Edit: Ignore the above, I forgot that 11.1.0.6 is not supported with 10.2.

Re: �??Version view�?� for tables\layers,

MarcoBoeringa — Tue, 08 Apr 2014 18:45:02 GMT

Could you please try it in your database? In case you create a table in the SQL enterprise database, does the version view is created automatically?

Jamal,

I tested this with ArcGIS 10.2 (so not the 10.2.1 you are using) and SQL Server Express 2012, and can't reproduce it. If I create an empty table, and register it as versioned, the Versioned View is automatically created.

I tried this workflow in SQL Server Express 2008 R2 and in Oracle 11g R2 (11.2.0.2) 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.

Again, I can't reproduce this with my configuration, what exact version of ArcGIS are you using William?

Re: �??Version view�?� for tables\layers,

Anonymous User — Tue, 08 Apr 2014 18:53:49 GMT

Original User: crafty762

I tested this with ArcGIS for Desktop Advanced 10.2.0.3348. Something is definitely off with the way the version view gets created, and it will take some in-depth testing on Esri's part to identify which configuration's work and which do not for this particular operation.

Re: �??Version view�?� for tables\layers,

JamalNUMAN — Tue, 08 Apr 2014 18:58:17 GMT

Jamal,

I tested this with ArcGIS 10.2 (so not the 10.2.1 you are using) and SQL Server Express 2012, and can't reproduce it. If I create an empty table, and register it as versioned, the Versioned View is automatically created.

Again, I can't reproduce this with my configuration, what exact version of ArcGIS are you using William?

Many thanks Asrujit and Marco for the input.

My software environment is ArcGIS 10.2 (and 10.2.1 on other machine) with SQL Server 2012.

In my case, if I create table (empty table from scratch) and register it as version then there is NO �??version view�?� is created.

What might be the solution here?
How one can have the version view created automatically as a table is created?

Re: �??Version view�?� for tables\layers,

Anonymous User — Tue, 08 Apr 2014 19:00:57 GMT

Original User: Jamal432@gmail.com

I tested this with ArcGIS for Desktop Advanced 10.2.0.3348. Something is definitely off with the way the version view gets created, and it will take some in-depth testing on Esri's part to identify which configuration's work and which do not for this particular operation.

Hi William,

How to get an answer about this particular issue from ESRI?

Re: �??Version view�?� for tables\layers,

Anonymous User — Tue, 08 Apr 2014 19:10:04 GMT

Original User: crafty762

Here is some information on how to report a bug. You can also open a support ticket with Esri Tech Support by calling or emailing them directly.

Also, I need to correct something I mentioned above... I incorrectly stated that I tested this functionality on SQL Server Express 2008 R2 above. Instead, this should have been SQL Server Express 2012. My apologies; I must not have had enough coffee this morning.

Re: �??Version view�?� for tables\layers,

MarcoBoeringa — Wed, 09 Apr 2014 13:10:23 GMT

I tested this with ArcGIS for Desktop Advanced 10.2.0.3348. Something is definitely off with the way the version view gets created, and it will take some in-depth testing on Esri's part to identify which configuration's work and which do not for this particular operation.

I am running exactly the same build of ArcGIS for Desktop. My SQL Server Express 2012 build is 11.0.3128.0, MDAC 6.1.7601.17514 on Windows 7 SP1.

In my case, if I create table (empty table from scratch) and register it as version then there is NO �??version view�?� is created.

What might be the solution here?
How one can have the version view created automatically as a table is created?

Jamal,

Unless you intend to access the Versioned View directly, either through ArcGIS, or more likely (because this is the main purpose of the Versioned Views), through non-ESRI software like AutoCAD or a SQL development environment, there is not much to worry about. The Versioned Views aren't required for correctly functioning ArcGIS software, nor for the versioned editing environment.

Versioned Views are a kind of "extra", non-compulsory, addition to the Geodatabase framework, so I wouldn't worry to much about Versioned Views not being generated in all cases.

Re: �??Version view�?� for tables\layers,

Anonymous User — Wed, 09 Apr 2014 17:47:12 GMT

Original User: coli4427

Jamal,

I read through the thread, and I notice that you are always logged into your sqlserver express instance as a user that is an admin, and therefore are mapped to the DBO user.

This maybe where the issue is, specifically with the sqlserver DBO user mapping when attempting to create the view during register as versioned.

The oracle case works because it does not have the same promotion semantics, my theory is that a dbms user would also work correctly on sqlserver enterprise, or as an OSA user who has not been granted admin privileges in sqlserver express.

This issue should be logged with support.

The hasVersioned view property is derived internally from the geodatabase metadata for the table (sde_table_registry.imv_view_name).

"System tables of a geodatabase in SQL Server"
http://help.arcgis.com/en/arcgisdesktop/10.0/help/index.html#//002q00000080000000

Colin

Re: �??Version view�?� for tables\layers,

JamalNUMAN — Wed, 09 Apr 2014 18:02:51 GMT

I am running exactly the same build of ArcGIS for Desktop. My SQL Server Express 2012 build is 11.0.3128.0, MDAC 6.1.7601.17514 on Windows 7 SP1.

Jamal,

Unless you intend to access the Versioned View directly, either through ArcGIS, or more likely (because this is the main purpose of the Versioned Views), through non-ESRI software like AutoCAD or a SQL development environment, there is not much to worry about. The Versioned Views aren't required for correctly functioning ArcGIS software, nor for the versioned editing environment.

Versioned Views are a kind of "extra", non-compulsory, addition to the Geodatabase framework, so I wouldn't worry to much about Versioned Views not being generated in all cases.

Thanks Macro.

The Version View is core issue at our workflow as it includes all the updates implemented on the business table. Our web mapping application (Geocortex) has the ability to connect between service layer and any SQL\Oracle tables. We are used to connect this service layer with the Version view as it includes all the updates.

[ATTACH=CONFIG]32974[/ATTACH], [ATTACH=CONFIG]32975[/ATTACH], [ATTACH=CONFIG]32976[/ATTACH], [ATTACH=CONFIG]32977[/ATTACH], [ATTACH=CONFIG]32978[/ATTACH]

At the moment, I couldn�??t link my layers with the EVW tables (new created tables) due to this issue. This is why I urgently need to have the version view.

what other options do we still have to create the Version view?

Re: �??Version view�?� for tables\layers,

Anonymous User — Wed, 09 Apr 2014 18:10:49 GMT

Original User: mboeringa2010

Jamal,

I read through the thread, and I notice that you are always logged into your sqlserver express instance as a user that is an admin, and therefore are mapped to the DBO user.

This maybe where the issue is, specifically with the sqlserver DBO user mapping when attempting to create the view during register as versioned.

Colin, you may be right. I now tested this by starting ArcCatalog under a Windows administrator account with sysadmin server role and DBO mapped to this login in the SQL Server database.

I indeed do not see a Versioned View being created on a new table, while it did when I started ArcCatalog normally under restricted account.