Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Permission not SysAdmin

Status
Not open for further replies.

djj55

Programmer
Feb 6, 2006
1,761
US
Hello, SQL2008R2
I get to take a week off, however that means they need a person permission to push table/stored procedure updates. I know I can grant the person SysAdmin rights and have done so in the past.

Is there a way to grant "modify and create" privilege for tables and stored procedures without granting the person SysAdmin role? Would this mean going to each database and granting permissions or can it be done globally?

Thank you,

djj
The Lord is my shepherd (Psalm 23) - I need someone to lead me!
 
Just grant them the db_owner role in the target database. If you need to worry about new databases appearing out of the blue, then you can grant them db_owner in the model database.
 
Thank you, I will do that.

I am not worried what he would do, but the auditors are getting picky about such things.

djj
The Lord is my shepherd (Psalm 23) - I need someone to lead me!
 
db_ddladmin role should allow them to create objects without being owners of the database. Try it...you might have to grant them db_datawriter also. If they need to grant permissions - db_securityadmin is what they need.

-SQLBill

The following is part of my signature block and is only intended to be informational.
Posting advice: FAQ481-4875
 
Grant permissions and creating databases are two things I do not want him to do.

For the big stuff the IT manager and CIO both have permissions. But tweaks to stored procedures are a daily occurrence, as our clients change things frequently, and the bosses do not want to have to push procedures all day.


djj
The Lord is my shepherd (Psalm 23) - I need someone to lead me!
 
db_ddladmin role is just on whatever database you grant it. Same as db_securityadmin role. Those aren't server roles. I would try just granting them the db_ddladmin role and having them test it by creating a fake stored procedure and fake table.

-SQLBill

The following is part of my signature block and is only intended to be informational.
Posting advice: FAQ481-4875
 
Sort of the plan. I was going to have him push the next stored procedure, but I guess I could use a dummy.

djj
The Lord is my shepherd (Psalm 23) - I need someone to lead me!
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top