ScottPletcher (1/14/2013)
opc.three (1/14/2013)
YSLGuru (1/14/2013)
opc.three (1/12/2013)
AD Groups as SQL Logins and Database Users work great unless you need the User to have a default schema. In SQL 2012 the loop has been closed, but this is a 2008 forum.@yslguru, I would look to rename them so they match the person's new name. Last name changes are pretty common and I rename Database Users and Server Logins all the time to keep up. Are you storing the Database User name in any audit tables? If the Database User name is used to maintain an audit trail then you may have a bit more to consider.
The schema that the app assumes for everything is 'dbo'.
If by 'assume' you meant that the app does not schema-qualify all object references and instead relies heavily on the default schema setup for each Database User then moving to AD Groups will not work for you until you move to SQL 2012.
I don't think that's true. While you cannot assign a default schema to the login, you can to the user. You just have to set it to "dbo" for each db for that group instead of at the login level.
From 2008 R2 BOL:
DEFAULT_SCHEMA cannot be specified when you are creating a user mapped to a Windows group, a certificate, or an asymmetric key.
Try it out though. You get an error when trying to set a default schema for a Database User based on a Login created from a Windows Group on 2008 R2 or below.
USE test
CREATE USER [DOMAIN\MyGroup] FROM LOGIN [DOMAIN\MyGroup] WITH DEFAULT_SCHEMA = [dbo];
Msg 15259, Level 16, State 1, Line 2
The DEFAULT_SCHEMA clause cannot be used with a Windows group or with principals mapped to certificates or asymmetric keys.
There are no special teachers of virtue, because virtue is taught by the whole community.
--Plato