SQL Server Permissions
-
If I give read-only access to a SQL Server login, does that mean they cannot call stored procedures that CRUD data? What I'm looking for is the ability for users to: 1. Read the database, 2. Execute stored procedures that CRUD data. But NOT run any DDL. Meaning they cannot change table structures or stored procedures. I'm sure there must be a way to configure this.
The difficult we do right away... ...the impossible takes slightly longer.
-
If I give read-only access to a SQL Server login, does that mean they cannot call stored procedures that CRUD data? What I'm looking for is the ability for users to: 1. Read the database, 2. Execute stored procedures that CRUD data. But NOT run any DDL. Meaning they cannot change table structures or stored procedures. I'm sure there must be a way to configure this.
The difficult we do right away... ...the impossible takes slightly longer.
So long as the user has permission to execute the stored procedure, and the stored procedure and the tables it references have the same owner, then it will work even if the user doesn't have any permissions on the referenced tables.
"These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer
-
So long as the user has permission to execute the stored procedure, and the stored procedure and the tables it references have the same owner, then it will work even if the user doesn't have any permissions on the referenced tables.
"These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer
Thanks, Richard!
The difficult we do right away... ...the impossible takes slightly longer.
