December 17, 2010 at 1:10 pm
I'd like to give a developer rights to add and drop a small list of tables. We are still on SQl2000. I want to exclude all other tables from this process. Is a stored procedure a good idea? Help please.
When the snows fall and the white winds blow,The lone wolf dies but the pack survives.
Once you've accepted your flaws, no one can use them against you.
December 18, 2010 at 11:44 am
Right, essentially what you want to do is to give the Database User the db_ddladmin Role but to a specific set of objects. Of course the problem is that you cannot define what the set is because they are going to keep moving in and out of existence 🙂
In SQL Server 2005 and above, the solution would be to create a Schema, within which the DEV Database User could CREATE and DROP table objects. Your on SQL 2000 so this is not a solution available to you.
I would suggest that you consider creating a separate database for this purpose or using temporary tables as an alternative.
December 20, 2010 at 12:11 pm
Yes, it's a pain. For now I think I have to give the user much more power than they need.
A co-worker suggested upgrading the database. A good suggestion. However I need to find a way to deploy the upgraded ODBC drivers to over 50 users. Perhaps SMS could do it.
When the snows fall and the white winds blow,The lone wolf dies but the pack survives.
Once you've accepted your flaws, no one can use them against you.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply