Post reply

Disabling CLR for Individual Databases

  • September 29, 2011 at 8:28 am

    #258030

    Is there a way to only allow CLR assemblies on specific databases rather than just an all or nothing approach?

    Thanks!

  • September 29, 2011 at 8:41 am

    #1388410

    since every CLR has a proc or function object, can't you create a role with DENY EXECUTE ON [each procOrfunction]?

    then put all the users in that role to take the ability to use them away?

    Lowell

    --help us help you! If you post a question, make sure you include a CREATE TABLE... statement and INSERT INTO... statement into that table to give the volunteers here representative data. with your description of the problem, we can provide a tested, verifiable solution to your question! asking the question the right way gets you a tested answer the fastest way possible!

  • September 29, 2011 at 8:48 am

    #1388420

    i believe this is the possible CLR types:

    select * from sys.objects where type_desc IN

    ('CLR_STORED_PROCEDURE',

    'CLR_SCALAR_FUNCTION',

    'CLR_TABLE_VALUED_FUNCTION',

    'CLR_TRIGGER',

    'AGGREGATE_FUNCTION')

    Lowell

    --help us help you! If you post a question, make sure you include a CREATE TABLE... statement and INSERT INTO... statement into that table to give the volunteers here representative data. with your description of the problem, we can provide a tested, verifiable solution to your question! asking the question the right way gets you a tested answer the fastest way possible!

  • September 29, 2011 at 8:50 am

    #1388422

    Sounds like a reasonable solution - not ideal but should work.

    I'll post after testing.

    Thanks.

Viewing 4 posts - 1 through 4 (of 4 total)

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