Restrict DDL to default Schema

  • I am sure that has been approached before, but I haven't found anything that I would consider to be a satisfactory answer. Here is my problem. I have two users, user1 and user2. Each user has their own schema, schema1 and schema2. The users should have the ability to issue dll statements within their own schema but should not have the ability to issue ddl statements against other any schema.

    I am trying to avoid the use of DDL triggers to pull this off.

    Thank you!

  • Maybe you could do something like this:

    DENY SELECT ON SCHEMA::SCHEMA1 TO User1;

    Or something like that?

    :cool:

    "There are no problems! Only solutions that have yet to be discovered!"

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

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