Re: Default schema not working properly for AD groups
- From: "Uri Dimant" <urid@xxxxxxxxxxx>
- Date: Wed, 13 Feb 2008 10:08:49 +0200
Camilo
According to SQL 2005 BOL, if a database user is mapped to an AD group,
the
default schema cannot be set and it will default to dbo.
A database user is mapped to Windows/SQL Login. Windows Login is a domain
account.
By deafult the objects are created with DBO schema. Can you post the script
to be tested?
"Camilo" <Camilo@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:F66B31E7-B929-4BD5-8BA2-A209CD03DB5A@xxxxxxxxxxxxxxxx
I have a customer that is trying to use AD groups to manage permissions for
a
SharePoint solution.
According to SQL 2005 BOL, if a database user is mapped to an AD group,
the
default schema cannot be set and it will default to dbo.
We have done several tests and this is NOT the case. What really happens
is
that a new schema is created for every member (account) of the group that
logs in and that schema becomes the default schema for each user.
We are running SQL 2005 SP2.
Is this problem addressed in some hotfix or is the product working as
designed? Any ideas?
Thanks!
Camilo
.
- Follow-Ups:
- Re: Default schema not working properly for AD groups
- From: Dan Guzman
- Re: Default schema not working properly for AD groups
- References:
- Default schema not working properly for AD groups
- From: Camilo
- Default schema not working properly for AD groups
- Prev by Date: Default schema not working properly for AD groups
- Next by Date: Re: Default schema not working properly for AD groups
- Previous by thread: Default schema not working properly for AD groups
- Next by thread: Re: Default schema not working properly for AD groups
- Index(es):
Relevant Pages
|
|