Hello everyone,
I'm experiencing an unusual issue with an Enterprise Geodatabase hosted on SQL Server. Specifically, I'm unable to delete a feature class within a dataset from ArcGIS Pro. When I attempt to delete the feature class, the process appears to complete successfully without any errors. However, after refreshing the feature dataset, the feature class still appears intact. Furthermore, I can add it back to the map without encountering any issues, and the data remains unaffected.
Some other information
Environment information
Has anyone else encountered this problem or have any suggestions on how to resolve it?
Thank you!
Solved! Go to Solution.
I've almost figured out what is happening with the issue. I created a new SQL user named 'gisadmin' and mapped it to the existing Windows login 'domain\gisadmin'. After doing this, I was able to successfully create and delete a feature class inside a feature dataset without any problems. It seems that the issue was related to the naming convention of the domain\username causing conflicts. This mapping resolved the problem.
Thank you for your assistance.
@VinceAngelo @George_Thompson Your support is highly appreciated
From my About page:
Note: Please do not try to message me directly or tag me in questions; just ask a question in an appropriate community, and if I see it, have something to add, and have the time, I'll respond.
Tagging me in questions is more likely to reduce the time I have to answer, and delay whatever response I might have.
- V
@VinceAngeloWell noted. I'm just hopped to get help as I cannot reach to technical support as our client is out of service contract and this is a production environment. Thanks for letting me know this policy.
When you try to delete the feature class. Are you logged in as "dataowner" or as your Windows user, just for clarification?
Can you provide all the permissions that the dataowner has, including any fixed-server and db roles?
What is the username / schema mapping, please provide screenshot.
I do appreciate your reply.
Thank you.
So, I ran a similar SQL for permissions and the difference I saw, was in the 'principal_type_desc' field. My data owner ("data") is a SQL_USER and not a WINDOWS_USER.
SELECT
USER_NAME(dppriper.grantee_principal_id) AS [USERNAME],
dppri.type_desc AS principal_type_desc,
dppriper.class_desc,
OBJECT_NAME(dppriper.major_id) AS object_name,
dppriper.permission_name,
dppriper.state_desc AS permission_state_desc
FROM sys.database_permissions dppriper
INNER JOIN sys.database_principals dppri
ON dppriper.grantee_principal_id = dppri.principal_id
WHERE USER_NAME(dppriper.grantee_principal_id) = 'data'
Can you please see if your login properties match something like this for the GISAdmin user?
@George_Thompson I have attached the loggin mapping screen. It seems the same as yours.
For the type of loggin (SQL User or Windows) Are there any differences or restrictions in case Windows login is used?
Not sure if there is a difference between the two......
I would highly recommend reaching out to technical support on this issue. Outside of the SQL vs Windows login, everything seems to be ok. I have also not seen that issue like this.
This is an update. I have created another geodatabase and dataowner user, and assigned the same privileges but for SQL login not a Windows login and successfully deleted a feature class in a feature dataset without any problems. I think it is clear for me now that the windows login is accused for this issue, but still I am not sure what is the problem with Windows login. Is there any specific permission or considerations should I take regarding the windows login in SQL server and Geodatabase?