Well, at least you can script out the sql statements using system objects
and some dynamic sql.
Kevin G. Boles
Indicium Resources, Inc.
SQL Server MVP
kgboles a earthlink dt net
Thanks for the idea Kevin. I am really looking to prevent someone
with this authority from dropping other objects. I have not yet
tested use of INSERT, UPDATE, and DELETE on the database.
DDL looks like the wrong way to handle. I am just trying to avoid
having to write a series of REVOKE statements for everything but
SELECT and CREATE/ALTER VIEWs. It seems a reasonable business
situation that you would grant these kind of permissions. Granting
full ALTER rights on the schema seems a bit much.