Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Database Role Design/Standard Expand / Collapse
Author
Message
Posted Tuesday, December 3, 2013 7:40 AM
Valued Member

Valued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued Member

Group: General Forum Members
Last Login: Wednesday, December 4, 2013 12:31 PM
Points: 52, Visits: 359
First, I apologize if this topic wasn't the right place for this post.

I am looking for a good standard for database role creation across my entire environment. I was hoping people might share what standard they use.

do you create the same database roles for each schema across all of your databases for consistency and assign database users to those roles as needed? Many roles would go unused, but having them available if needed might not be a bad thing.

do you primarily use the built in database roles?

do you just create them as you need them? (this has led to inconsistency in our environment).

I think consistency would be nice for ease of administration, but I would like to know what other people are doing. There might be a great solution out there that I'm just not thinking of...

Thank you :)
Kim
Post #1519230
Posted Tuesday, December 3, 2013 10:54 AM


SSChampion

SSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampion

Group: General Forum Members
Last Login: Today @ 6:28 AM
Points: 14,198, Visits: 28,526
I very seldom use the built-in roles. I always build the roles custom. but, I only build them as needed. Not all roles are ever needed on all databases. And, some roles are unique to some databases. I'm a fan of consistency, but only where it's actually serving me. I don't like consistency just for consistency's sake.

----------------------------------------------------
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood..." Theodore Roosevelt
The Scary DBA
Author of:
SQL Server Query Performance Tuning
and
SQL Server Execution Plans

Product Evangelist for Red Gate Software
Post #1519328
Posted Wednesday, December 4, 2013 12:27 PM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: 2 days ago @ 7:11 PM
Points: 7,920, Visits: 9,646
I mostly used the built-in roles, but because using only teh built-in roles would sometimes mean either splitting data I want to have in one database over two (or more) databases (preventing some highly desirable uses of declarative referential consistency) or giving some logins more privileges than ideally they should have I sometimes made custom roles. In my experience it is rare for a custome role to be common to many databases, so not making the roles the same in every database reduces clutter - and I certainly don't see it as promoting inconsistency.

Tom
Post #1519756
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse