Sunday, February 19, 2012

dbo puzzle

Hi,

I managed to get things broken and I can't solve it:

Scenario:
SQL Server
>Databases
>TestDB
> Users
> dbo mapped to user1 (user1 = SQL Server user)
> user1(database user) mapped to nothing (no SQL user)
->Security
-> Logins
-> user1

Problem: I don't want SQL Server user 'user1' to be dbo but I can't remove dbo rights because it owns objects nor can I drop database user 'user1' or delete SQL Server user 'user1' because it's mapped to dbo.

I'm running in circles..
First and last time I use the auto_fix option to fix orphaned users.
At this point, the only solution to me is dropping the database.

Anyone with a better idea?

Thank you!
Best Regards,
Worf

Have you tried these steps, in this order?

1. Create another user, User2

2. Add User2 to db_creator role

3. Transfer ownership of each object owned by User1 to User2

4. Remove dbo rights from User1

5. Remove User1 from db_owner role

6. Remove User1 from sysadmin role

7. Transfer ownership of each object owned by user2 to dbo

8. Remove User2 from db_creator role

9. Remove User2

10. Remove User1 if desired.

|||

which version of sql server is this? i believe SQL Server 2005. in that case this user1 might be owner of schema User1 and USER1 schema is the owner of objects. what need to do is change the owner of schema by


ALTER AUTHORIZATION ON SCHEMA::[User1] TO [dbo or whichever schema u want to transfer]

then drop the user

Madhu

No comments:

Post a Comment