Select to view content in your preferred language

Seeing relationships from other data creator in a particular data creator SDE connection

208
1
11-26-2024 03:55 AM
ApurvDanke
Regular Contributor

Hello,

We have upgraded a geodatabase from 10.6.1 to 10.8.1 using an SQL Server backup file extracted from production environment. This is also an ArcFM enabled database including Fiber Manager, where ArcFM has been upgraded from 10.6.1 to 10.8.1c.

Broadly we followed these steps.

  1. Restore the database from backup file in a new instance of SQL Server.
  2. Upgrade ESRI geodatabase from 10.6.1 to 10.8.1 using upgrade geodatabase geoprocessing tool.
  3. Upgrade ArcFM and Fiber Manager from 10.6.1 to 10.8.1c.
  4. Applied all necessary privileges and permissions to data creators such as Electric, Water, Fiber users (schema owners) in SQL server. Provided all the permissions to SDE user in SQL server.

We're observing few things.

  1. After logging in with Electric user (schema owner for Electric data) we can see Electric datasets, Electric relationships but we can also see relationships from other data creators such as Water, Fiber etc. As per our client, this should not happen. Only Electric data and Electric relationships should be visible.
  2. If we connect to geodatabase using Electric user, we can view the properties of Electric relationships correctly, but if we check properties of Water or Fiber relationships we get an error - 

ApurvDanke_0-1732622060971.png

3. We see all the objects in geodatabase whether it is feature dataset, feature class, table or relationship - all of them are named as [DatabaseName].[DataCreatorUser].[ObjectName]. For example a feature class for Fuse is named as ABC.Electric.Fuse. Where ABC is our database name. This is unusual. Usually the format should be Electric.Fuse. Same is observed for other objects like feature dataset, table or relationship.

Following permissions have been provided to Electric user in SQL Server (15.x).

Database Level Permissions - Connect, Create Procedure, Create Table

User Memberships - None

Permissions given on SDE schema - Execute, Select

Permissions given on Electric schema - Electric user is owner of this schema

Database Role Membership - Public

 

We tried giving database role membership "db_datareader" and it fixes the issue for relationship error for other data creator owned relationships such as Water (#2 above in observations), but it introduces another issue which is that all the other datasets belonging to other data creators are also visible to Electric user.

 

Any reason why we're observing the points 1-3 above? Any solution or workaround for the same?

Regards,

Apurv

0 Kudos
1 Reply
MarceloMarques
Esri Regular Contributor

Yes, the relationship classes will show up. This is expected, and unfortunately, there is nothing we can do to filter those out.
I recommend you to open a support ticket with Esri Support and/or Telvent ArcFM Support once this is an ArcFM Geodatabase if you need further clarification.
https://arcfm.my.site.com/myarcfm/s/login/
Note, besides the upgrade of the Geodatabase ArcSDE Repository is also necessary to upgrade the ArcFM Repository.
https://myarcfm.schneider-electric.com/myarcfm/s/article/Upgrade-to-10-8-1

| Marcelo Marques | Esri Principal Product Engineer | Cloud & Database Administrator | OCP - Oracle Database Certified Professional | "In 1992, I embarked on my journey with Esri Technology, and since 1997, I have been working with ArcSDE Geodatabases, right from its initial release. Over the past 32 years, my passion for GIS has only grown stronger." | “ I do not fear computers. I fear the lack of them." Isaac Isimov |
0 Kudos