nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

'Hiding' Relationship Classes in Enterprise GDB

JoeBorgione

Version 10.3.1, SQl Server 2012:

Is there a way to 'hide' a relationship class in an enterprise geodatabse? The users do not have any privileges to read (select) the feature class and table in the relationship class, but the relationship class itself shows up for them:

#relationship class #sde privileges‌ #privileges‌

タグ付けされた投稿をもっと見る

Accepted answers

Asrujit_SenGupta

No, we cannot.

At 10.2.2, they added the functionality of not showing Feature Datasets, however nothing for Relationship Classes yet.

FAQ: Can feature datasets be prevented from appearing under Database Connections in ArcCatalog?

As far as I can remember, whatever data is present within a Feature Dataset, will be hidden from a user if that user doesn't have privileges on the dataset. However if these objects are outside a feature dataset, it will still be visible to a user who doesn't have privileges on it.

There was an Enhancement logged for this a couple of years back:

ENH-000085148 - Do not return relationship class for which the connecting user has no access to its related data

However, you will have to contact Esri tech Support if you want to know the current status of the Enhancement request.

Geodatabase‌ Managing Data‌

All comments

FrankSimeknaperville

Eight years into this thread and this workaround confuses me.

The option (ArcGIS Pro > Options > Catalog Browsing > Browse project items > List only objects owned by the connecting user) is another added layer unto an already vast mosaic of options, configurations, settings, and preferences in the ArcGIS experience. Could an expert at Esri explain, technically, why the visibility of the relationship class object does not conform to the the same permissions set for both schema owners and database roles as they do for the feature classes and tables that participate in those same relationship objects? In other words - why is this an option, and, when would we ever NOT enable it?

I put in a ticket with Esri to check on the status of ENH-000085148: Esri Support replied that it was closed - 'Will Not Be Addressed'.

There is another enhancement ENH-000130871: "Please do not return relationship classes over enterprise geodatabase connections when the connecting user does not have permission to the related data" that is 'In Review', submitted 5/13/2020, last updated 5/21/2020. Esri Support said the workaround mentioned in the enhancement is "If the related data is in a feature dataset, the dataset and the relationship class are hidden correctly."

NigelGriffiths

Does anyone know whether this is resolved yet? We have many relationship classes showing up for all SDE connections, despite SDE connections having no visibility of associated datasets.

AndresCastillo

Hi @Raj-Chavada

Sorry, I have not explored this option yet in ArcGIS Pro.

Raj-Chavada

Thanks @AndresCastillo for the workaround. Is there an option to carry out the same change in ArcGIS Pro?

AndresCastillo

My team was discussing a workaround:

In ArcCatalog there is a setting to view only the data owned by the owner.

ArcCatalog-> Customize > ArcCatalog Options > Check box 'List only objects owned by user'.

This will work only for owner connections.

When you try to connect with other schemas that have privileges to the owner objects, then ArcCatalog will not display anything.

listOnlyOwnedGDB.png

screenshot.docx

SandraWang2

Does anyone have any solution or workaround for this? Thanks

SandraWang2

What is the solution for this? I have a GEodatabase has so many relationship class and it's very annoying that other schemas (users) an see it automatically.

Is there any other workaround for this?

Thanks in advance .

JackChen1

Without permission, a user (husband) can peek at the relationships in the world of another user (wife). Good job, ESRI. You expose users' privacy.

For an enterprise geodatabase (ArcGIS 10.5.1) atlas in an instance of SQL Server 2014, I created 9 users/schemas. The schema gio associated with user gio owns its two feature classes (FireDistricts, Tax_Parcel_Polygon). No any permission for user gio to do anything on other data in other schema. However, the user gio can still see the relationship classes in the schema laurens associated with the user laurens.