July 14, 2003 at 5:13 am
How can I prohibit dropping of a table.
Table SYSOBJECTS cannot have triggers.
July 14, 2003 at 8:48 am
Put the user in a database role that doesn't have db_owner or db_ddladmin priviledges (i.e., put them in the "public" role assuming that you have not GRANT rights under "public" for dropping tables).
All the best,
Dale
Edited by - DALEC on 07/14/2003 08:52:19 AM
Edited by - DALEC on 07/14/2003 08:54:44 AM
All the best,
Dale
Author: An Introduction to SQL Server 2005 Management Studio
July 14, 2003 at 9:56 am
If the users need to maintain high level rights, and you are only trying to avoid accidental drops, you could create a schemabound view on the table in question. This would prevent anyone from dropping the table until the view was removed.
Essentially, you would create an indexed view, without the pesky index.
Dan
July 14, 2003 at 10:43 pm
I'm very grateful to DALEC and scrilla99
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply