September 6, 2006 at 8:37 am
This is a well-known issue with sql 2005 but my question is what's the best way to handle this Administratively?
For "ordinary" (400+) users I plan to create Windows AD groups and assign each group a database role (but no schema of course). Given the users will have no assigned schema, I believe that each user will default to the "dbo" schema. (Then we need to harcode all table names, stored proc names, t-sql references, etc with the "dbo." prefix. Time to review the old code...). This "emulation of sql 2000" will have to do until Microsoft addresses the issue or unless someone can suggest a better approach.
For "dbo" users I am taking their AD account and assigning it permissions on the local sql 2005 server box. (No groups will be used for them.)
TIA,
Bill
September 21, 2006 at 8:10 am
This is by design. Group cannot have a default schema, since no principal can have group as its primary id (as opposite to group id). Consider following: windows user1 is added to windows group1 and group2. If both of them are allowed to have default schema what default schema user1 has then?
Viewing 2 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply