Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
ravilobo
Master Smack Fu Yak Hacker
1184 Posts |
 Posted - 2010-03-28 : 23:40:05
|
| I have an AD group login that contains all the developers. However, there is also a need for the developers to create their objects in their own schemas. How to achieve this? I have a brick and mortar solution – however, I don’t want to set the boundaries for the visionaries. ------------------------I think, therefore I am - Rene Descartes |
|
|
russell
Pyro-ma-ni-yak
5072 Posts |
Posted - 2010-03-29 : 12:55:25
|
| just change their default schema. |
 |
|
|
ravilobo
Master Smack Fu Yak Hacker
1184 Posts |
Posted - 2010-03-30 : 08:59:00
|
quote:
Originally posted by russell
just change their default schema.
There is only one login at the server level that gives access to all the underlying members!------------------------I think, therefore I am - Rene Descartes |
|
|
|
russell
Pyro-ma-ni-yak
5072 Posts |
Posted - 2010-03-30 : 10:14:11
|
Not a good idea if you don't want all users treated the same.Anyway, in this case, the developers need to specify the schema they're creating the objects in:Create Table mySchema.myTable(...)Create Table yourSchema.yourTable(...) |
|
|
|
ravilobo
Master Smack Fu Yak Hacker
1184 Posts |
Posted - 2010-03-30 : 11:39:12
|
| I thought so too. Thank you Russel.------------------------I think, therefore I am - Rene Descartes |
|
|
|
|
|
|
Group access and independent schema objects