Database User Role Management

Hi Experts,
I need an answer to the design of an application with Microsoft SQL Server 2008 R2 and Active Directory as the security model.

We have roles in the application for groups of users:
e.g. Manager...etc...etc.
The Manager role is an Active Directory Security Group and added under "Security/Users" in SQL Server.
We assign each role various permissions on stored procedures so they can peform their job function.

Recently we expanded our application to multiple databases. We also ran into the isuse where some users are allowed access as a Manager to one database and not another. Some Managers require access to all databases.

How can I plan the user management so that all users are restricted to one database and a role?
Can I use the existing Active Directory and use a clever design or do I need to change the code?

What I have been told by my developers is this which I don't like!
I would have to created many security groups and assign users individually based on database and role.
and then map these roles to each of the databases. It would also mean having to add users multiple times. Considering we could be expanding to 30+ databases this seem very messy to me and not the best design.

I would appreciated you knowledge and experieince on this problem.
Thanks in advance.
LVL 10
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

MySQL is not SQL Server.  Please click on Request Attention and have the zones changed.  Thanks.
Steve BinkCommented:
Your developers sounds like they are on the mark.  You can create a single role that provides access to all the databases, but you will need a new role once you have a user that requires access to only a single, or several, databases.  The alternative is to apply the settings directly to the users or AD group, but that is really just abstracting the same work into AD instead of SQL Server.  

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
.NET App Servers

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.