Permissions to Run CLR Assembly

Question

Permissions to Run CLR Assembly

hawg

SSCertifiable

Points: 6044
More actions
April 7, 2020 at 12:56 pm

#3741021

This is my first time dealing with CLR assemblies and we have setup some CLR assemblies in one of our databases and created some stored procedures to access these assemblies. Now I need to give a particular user permission to run these stored procedures. I have granted EXECUTE on the stored procedures but this user is not able to successfully run the procedure. The procedure does work because we can run it as a user that is part of the db_owner role.
I am just trying to figure out what other permissions I need to set to allow a regular user to run the stored procedures that run the CLR assemblies. Can someone point me in the right direction.
----------------------------------------------------------
01010011010100010100110000100000010100110110010101110010011101100110010101110010
001000000101001001101111011000110110101101110011

Viewing 3 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic. Login to reply

hawg SSCertifiable Points: 6044 More actions · Answer 1

I can't find a way to delete this post so I just want to supply an update. The EXECUTE on the stored procedures worked just fine. The issue was in the CLR code. Once we got it worked out, there was no more issue.

----------------------------------------------------------

01010011010100010100110000100000010100110110010101110010011101100110010101110010
001000000101001001101111011000110110101101110011

Jeff Moden SSC Guru Points: 1003851 More actions · Answer 2

What would be more interesting is what the CLR assemblies actually do. A lot of people resort to CLR simply because they don't know how to do something in T-SQL. I'm pretty sure we can help there.

--Jeff Moden

RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
First step towards the paradigm shift of writing Set Based code:
________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

Change is inevitable... Change for the better is not.

Helpful Links:
How to post code problems
How to Post Performance Problems
Create a Tally Function (fnTally)