March 8, 2016 at 10:57 am
We have about 30 devs that all work on different projects and SQL databases. Dev A and B needs access to DB1,DB2 and DB3 But Dev A also needs access to DB4.
Does anyone else have a problem managing Dev's DB SQL access? and do you have any recommendation?
March 8, 2016 at 11:19 am
Talk with your network admins and have them create AD groups to manage the different granular access levels needed. Assign your devs to the correct AD groups.
Register those AD groups to the server and you should be good. Any changes to the access should be done in AD not on the actual SQL box.
March 8, 2016 at 11:50 am
Thank you. I have control of the AD and would be able to create Active directory groups and add users in.
Our structure has a lot of crossing of databases. Our environment has over 100 DBs like this and a lot of crossing of access.
For example:
Database Names: DB1,DB2,DB3 and DB4
Bob =access to ALL DB's
Jane= DB1,DB2,DB3
Sally= DB2,DB3,DB4
John= DB3,DB4
Does anyone else have this kind of problem and how did they solve it?
March 8, 2016 at 4:31 pm
Does anyone know any good programs to manage SQL logins both Windows auth and SQL auth in one place for many servers?
March 9, 2016 at 5:43 am
It's also a good idea to use roles within the database to assign permissions through the role rather than to individual AD groups. This makes it easier to mix and match permissions at multiple levels.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply