I noticed another difference between UserA and UserB: On TheDb properties, tab Permissions, sub-tab Effective: Msg 259 Ad hoc updates to system catalogs are not allowed. = roleprinc.)īut I am not able to edit these tables (even with sysadmin role), which is understandable. Left outer join sys.database_principals roleprinc ON roleprinc. Left outer join sys.database_principals memberprinc on memberprinc. Here is a query showing that: - Users that are members of roles without any permission : This Stack Overflow answer put me on the track. Windows AD account.ĭo you know a way to have more information about a potential Windows AD account specific permission?Īfter much more research, I suspect that UserB has a role with no permission. So, to me, the only difference left is local account vs. But I do not want to let it have this role.
If I add sysadmin role on UserB, of course, it has the permission. I tried to grant the permission explicitly for UserB : GRANT SELECT, UPDATE, DELETE, INSERT on TheTable TO The accounts are not members of the role db_denydatawriter. One of these roles has the permission to INSERT/UPDATE/DELETE on the tables. 'TheTable', database 'TheDb', schema 'dbo'Īs far as I know, the two accounts have the same roles.
The INSERT/UPDATE/DELETE permission was denied on the object It is a member of Administrators group on the database server. It is a SQL Server 'local' account (a SQL Server login, NOT a Windows Account on the local server). UserA (SQL Login): can do these commands (on any table). SQL Server version is 2008 R2 (, 64 bits). I have two SQL Server user accounts on a database that behave differently on INSERT / UPDATE / DELETE.
0 kommentar(er)
