Enable SQL Access - Versioned Views

5109
11
Jump to solution
02-19-2015 06:31 AM
Highlighted
Occasional Contributor

Hello,

To give a little context on the actual situation;

- We have an enterprise GDB in which changes are made along daytime in large quanitities.

- The GDB is registered as versioned.

- The compress process is made two times in the day at 12h and 0h.

- In a parallel process, another application intends to give a report in real-time using data from an alphanumeric database.

- This application needs to retrieve the spatial data directly from SQL tables.

- Due to some active connections, the compress level never reaches level zero, so the tables in SQL don't reflect all changes made in ArcGIS.

So, my issues are the following:

- The "Enable SQL access" option in ArcCatalog is always disabled (The connection to the GDB is made with a sysadmin user in SQL)

- Is there a way to reach level zero in the compress?

0 Kudos
1 Solution

Accepted Solutions
Highlighted
MVP Esteemed Contributor

How are you "seeing" the geodatabases tables?  Are you logging into SQL Server using SQL Server Management Studio (SSMS) or SQLCMD?  If the former, are there no views showing up under the Views folder/tab?

sql_server_mgmt_studio_listing_views.PNG

Originally with 10.1, versioned views ended with "_VW" but Esri changed that in 10.2 to end in "_EVW".

View solution in original post

11 Replies
Highlighted
MVP Esteemed Contributor

Starting with ArcGIS 10.1, versioned views are automatically created for tables or feature classes that are registered as versioned.  Are you sure the "Enable SQL Access" isn't greyed out because a versioned view already exists?

Highlighted
Occasional Contributor

Joshua,

Inside SQL there are not such thing as versioned views.

I can see a&d tables, also some "i" tables and the tables corresponding to the feature classes but nothing as "evw" tables. Is there another way to reach them?

Tks

0 Kudos
Highlighted
MVP Esteemed Contributor

What DBMS are you using?

0 Kudos
Highlighted
Occasional Contributor

SQL Server 2012

0 Kudos
Highlighted
MVP Esteemed Contributor

How are you "seeing" the geodatabases tables?  Are you logging into SQL Server using SQL Server Management Studio (SSMS) or SQLCMD?  If the former, are there no views showing up under the Views folder/tab?

sql_server_mgmt_studio_listing_views.PNG

Originally with 10.1, versioned views ended with "_VW" but Esri changed that in 10.2 to end in "_EVW".

View solution in original post

Highlighted
Occasional Contributor

I'm so embarrased!!!

Sorry I made you lose your time!! It seems that I was so into this that I never saw the "Views" folder

Thamk you so much and sorry again

0 Kudos
Highlighted
MVP Regular Contributor

Nothing to be embarrased about or to apologize for. We have all been there trying to make sense of the Geodatabase concept and all the documentation.

Glad to have been of help, and certainly check out that Help page I linked as well!

0 Kudos
Highlighted
MVP Regular Contributor

Marco Alejandro Bonilla schreef:

Joshua,

Inside SQL there are not such thing as versioned views.

I can see a&d tables, also some "i" tables and the tables corresponding to the feature classes but nothing as "evw" tables. Is there another way to reach them?

Tks

They aren't listed under tables, they are database views! You should look under Views in SQL Server Management Studio to find them...

Instead of fruitlessly trying to compress to state 0, you may also consider connecting to a specific version using versioned views. This may give a more "recent" picture, although it won't resolve all your issues, as it will not show edits going on in any other specific versions.

You can find more information in this particular Help topic, especially see the remark about the set_current_version ability of versioned views:

What is a versioned view?

Highlighted
Esri Esteemed Contributor

Hi Marco,

In order to compress to a state of 0, you will need to make sure no users are connected.  So, you will need to disconnect all active users, and then perform the compress.  Take a look at the following link:

ArcGIS Help 10.1

0 Kudos