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 |
|
tfountain
Constraint Violating Yak Guru
491 Posts |
 Posted - 2009-07-02 : 09:11:54
|
| Ok, so if SQL Server 2005 implemented user / schema separation, when I create a database user, why does a schema of the same name get created? Let me describe our scenario. All of our SQL Server access is done through SQL logins. The login can be through a domain group, domain account or a SQL login. Next, any database access is controlled through this SQL login. When I give permissions (lets say through the GUI) to a certain database, both a user and a schema is created in that database.In our model, the users do not necessarily need to have schemas created. We do use schemas but they have nothing to do with users (i.e. dbo by default of course, schemaA, schemaB, schemaC, etc) - rather more of a product line.So, my question is this - is there a way to either (a) not create the schema in the database to begin with or (b) what is the recommended method for removing or disabling the schema? |
|
|
|
|
|
User / Schema separation questions...