-All
I need to setup a group of people in SQL Server as follows:
1) Insert/Update/Delete/Selec
2) Create, Drop, Alter Functions or Procedures as any owner.
3) Can Not create tables.
4) Can Not create views.
5) Can Not create indexes.
6) Can execute any job.
7) Can Create/Alter/Drop any DTS package.
I figured out how to setup the first four requirements, but I'm stumped on the last three.
For the first four I:
Created a new role called db_deny and added the
- Deny Create Table
- Deny Create View
privilges to the role.
Then I added the ddl_admin, db_datawriter, db_datareader and db_deny roles to the group of users. This addresses the first four as a user can now read/change any data, modify any code (and set owner to dbo) and they cannot create tables or views. However they can still create indexes, they can create DTS packages but the package is then owned by this person and no one else can modify it. Additionally, they can only see jobs that they own so they can't run any job, so I clearly haven't addressed the remaining issues. It just seems like all of SQL Servers security is at such a high level that its effectively useless because I have to grant so much authority to do the simplest things.
Any help is appreciated, this ones worth a lot to me.
Thanks
-Wes
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Save solutions to your questions, answers you’ve discovered through searching plus helpful articles in your personal knowledgebase for easy future access.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.
Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
wes_wilson:
This old question needs to be finalized -- accept an answer, split points, or get a refund. For information on your options, please click here-> http:/help/closing.jsp#1
EXPERTS:
Post your closing recommendations! No comment means you don't care.
Business Accounts
Answer for Membership
by: ispalenyPosted on 2003-04-08 at 14:25:22ID: 8295174
Q. Can Not create indexes...
A. Sysadmin, db_ddladmin and db_owner can use CREATE INDEX. Nobody else. Your users are in ddl_admin group, you must remove them from this group.
Q. Jobs and the security
For jobs you can try to create a system procedure to change an ownership of the job from a single user to a user group.