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 |
|
bbxrider
Starting Member
37 Posts |
 Posted - 2010-04-07 : 21:13:55
|
| this is actually 2005 studio express, and am not sure at this point what the differences are but hopefully same for this issue.i added the aspnet user for some testing and mistakingly gave permissions for the schemas as well as tables. now i want to remove those schema permissions but they are displayed with a green box instead of a check and can't remove them. i see that i can change it to another user such as dbo but is that the solution? since i'm new to sql server i'm not sure about the consequences of that. the original db was created by visual studio for a login control and the orig didn't have any users as schema owners and i would like to get back to that state. |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
|
|
bbxrider
Starting Member
37 Posts |
Posted - 2010-04-08 : 02:37:03
|
| and then thats it? just leave it that dbo now owns schemas? and there is no way to ever get the schemas from being owned by some user? when vs creates this db (to implement login security) it did not set dbo to be the owner of anything, that i have seen so far, its ok to just change all that around? |
 |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
|
|
chewtoy
Starting Member
1 Post |
Posted - 2010-10-14 : 17:59:08
|
| If memory serves me, these Schemas by default actually own themselves. In other words, if you select the database in question, and expand the Security node, and then the Schemas node, you can view properties on each Schema for that db. Once in the properties page for a Schema, you can change the owner to itself, thereby "removing" the owner you accidentally set in the first place.Tara: If we always use dbo, then why have schemas in the first place? |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
|
|
|
|
|
|
|
remove schema ownership
It was added to be more like Oracle, but I don't think it's been adopted much in the SQL Server community.Tara Kizer