Latest Contributions by AfreenVirani

Hello Allison, When a relationship class is created between two objects (tables, feature classes, etc.) you want to make sure that the user (viewer/editor) has permissions to view/edit BOTH the objects. It is not required to revoke and regrant permissions to the objects to be able to access them if sufficient privileges are applied to begin with. I do notice, however, that you may be at an unsupported version of SQL Server for ArcGIS 10.6.1. The minimum supported SQL Server database for ArcGIS 10.6.1 is SQL Server 2012 SP3. Strange behaviors are commonly seen when unsupported versions are used, so it could be a possible cause of the issue you are seeing. For your reference, I have listed below documentation that highlights the Microsoft SQL Server database requirements for ArcGIS 10.6.x: https://desktop.arcgis.com/en/system-requirements/10.6/database-requirements-sqlserver.htm I hope this helps! Thanks, Afreen ... View more

No problem! In ArcCatalog, if you right-click on your geodatabase connection > 'Connection Properties' you should see the user that you are connected as by 'User name'. To connect as the WAYNECOUNTY user you would type in "WAYNECOUNTY" as the username, and a corresponding password for that user. (If you do notice that you are in fact connected with the user name "WAYNECOUNTY", then you would need to ask the SQL Server database administrator to remove the db_owner privilege from this user.) ... View more

Hello Paul, When trying to copy/paste or import data into a feature dataset inside an enterprise geodatabase the copier/importer must be the user that owns the feature dataset. Naming convention in SQL Server: <database_name>.<data_owner>.<feature_class_name> It looks like you are trying to import the shapefile into a feature dataset that is owned by the user "WAYNECOUNTY". Since you are part of a group that has the "DB_owner" privilege, you are being recognized as "dbo" Ex: <database_name>.DBO.<feature_class_name>. Therefore, when you are trying to create the data in that specific feature class it is recognizing you as "dbo" hence an error is thrown. You  could do the following: 1 - Connect to the geodatabase as the "WAYNECOUNTY" user, and then import the shapefile into the feature dataset. If the "WAYNECOUNTY" user has the db_owner role, then remove the db_owner role from this user. or 2 - Create a new feature dataset as the existing user - which will be created as "gisdata.dbo.administrativeareas" and then you would be able to import as a feature class into this feature dataset. Best, Afreen ... View more