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.
We're observing few things.
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
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