Permissions for executing a stored procedure
From: DeeJay Puar (deejaypuar_at_yahoo.com)
Date: 05/19/03
- Next message: Mike Cassara: "CREATE VIEW Permissions in SQL Server 2000"
- Previous message: Michael: "Permissions for executing a stored procedure"
- In reply to: Michael: "Permissions for executing a stored procedure"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Mon, 19 May 2003 08:16:19 -0700
Hi,
Truncate table permissions only default to table owner,
members of sysadmin, db_owner, ddl_admin and CAN NOT be
transferred.
So, eventhough, you have granted execute permissions to
stored procedure, the user also needs to part of one of
the roles mentioned above.
Instead using TRUNCATE TABLE, you could use DELETE FROM,
which is slower and logged I believe.
hth
DeeJay
>-----Original Message-----
>We have a stored procedure that has code in it to
truncate tables. We do
>not want to grant DDL permissions to the user id that is
going to execute
>this stored procedure. From what I've read it seems like
I should be able
>to grant the user "execute" permissions on that specific
stored procedure,
>and even though the user does not have DDL permissions,
the store procedure
>should run successfully. But when the user runs the
procedure they are able
>to execute it, but as soon as it tries to truncate the
table it craps out
>saying the user doesn't have the proper authority. Any
suggestions?
>Thanks!
>
>
>.
>
- Next message: Mike Cassara: "CREATE VIEW Permissions in SQL Server 2000"
- Previous message: Michael: "Permissions for executing a stored procedure"
- In reply to: Michael: "Permissions for executing a stored procedure"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|