New answers tagged permissions
As you can see you have RESOURCE role granted to the user user_kshitz. And you have to query the ROLE_SYS_PRIVS. SQL> select * from role_sys_privs where role='RESOURCE'; ROLE PRIVILEGE ADM ------------------------------ ---------------------------------------- --- RESOURCE CREATE TRIGGER NO ...
According to MySQL documentation, in order to change a password of a user, bmcrae must have UPDATE privilege for the mysql database. To check the privileges of the user bmcrae, run the following command: show grants for 'bmcrae'@'hostname'; OR Show grants for bmcrae; And check whether, the user bmcrae has UPDATE privilege on mysql database. If the ...
Try running this, when in the Database - it will give you the permission levels for SERVER, DATABASE, OBJECTs in 3 separate result windows - you can then consider the Group membership of the user vs the permissions levels (copy/paste results into Excel for easier filtering, etc. (PS. not my code, but very useful - I would reference the original ...
I would check if the users are part of the db_denydatareader role, check for deny permissions on the tables schema, and also for a deny permission on the public role. I would suspect these are the most likely culprits.
I found the answer to be, CASE (SELECT RoleType FROM user) WHEN 'standard' THEN GRANT PROXY ON 'standard_user'@'localhost' TO CURRENT_USER(); WHEN 'admin' THEN GRANT PROXY ON 'admin_user'@'localhost' TO CURRENT_USER(); END CASE;
The user needs to be the owner of a schema to get any rows from information_schema.schemata alter schema $schemaName owner to $user; Or the user needs to be a member of a group that owns the schema Usage grant is not sufficient. The user does not need to be a superuser. The user can own a table in a schema, but that is not sufficient either.
Short Answer: Try changing the default database of the dev user to their particular database. In the Query window within SS Studio, make sure they're using the right database context within the Query window via the database drop-down list or T-SQL USE [DBNAME]. Long Answer: I cannot speak for every circumstance but I know a case where this definitely ...
Yes. What you have will do what you want. I do question the need for UserA to have db_owner access even on database A though. Do they have a need to be able to drop the database? Run backups that could interrupt your backup chain? Change recovery model (same problem)? Generally even if a developer has complete control over a given database I would ...
Interesting one - difficult to pin this one down. Have you thought about looking at the public role? sp_helprotect 'CREATE PROCEDURE',NULL,NULL,'s' Does that bring you back anything?
Top 50 recent answers are included