January 28, 2008 at 8:07 am
Some developers recently implemented a CLR stored procedure that returned an error with update permission denied on table name. Once I granted the user account update permission on that table, it was able to execute OK.
I am trying to find information on the permissions a CLR stored procedure needs when it accesses tables. A dbo TSQL stored procedure has permissions on all dbo tables for select, insert, update, and delete, so there is no need to grant permissions on tables to the database user. I am not looking for the permissions that I have to grant on the CLR procedure to be able to execute, but how to configure the permissions on tables in order for the CLR procedure to be able to access them.
I have been looking for a good explanation for the way the permissions to database objects need to be setup for CLR stored procedures. For example, could I have modied the procedure to use the EXECUTE AS clause, instead of granting the user account direct permission on the table? Does anyone have any links to good articles on this subject?
I've been searching the web for some time, and I haven't found anything that directly addresses this.
January 29, 2008 at 8:16 pm
bump
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply