I'm having difficulty getting SQL Server to cooperate with assigning a database user to a login. I want a user besides dbo assigned to the Oak/Dennis login for the MAXCOPY database. However, when I try to make that assignment I get the error that user dbo cannot be dropped.
Notice the user mappings of the Login properties in the attached screenshot. In this case, Oak/Dennis is a brand new login. For some reason, it assigned Oak/dennis for the user of the AdventureWorks and Miller databases, but i assigned dbo for the user of the MAXCOPY database. I want Oak/dennis to be the user of the MAXCOPY, as well.
FWIW, a couple of other odd symptoms I'm experiencing are:
I cannot uncheck the mapping for MAXCOPY or MAX_Struct--it gives the same error "cannot drop dbo"
I cannot create a user called oak\dennis in the MAXCOPY database--I get an error "the login already has an account under a different user name"
I experience similar problems with other users in the two problem databases
I don't experience this problem with the Adventureworks or Miller databases
Any ideas, how I can reassign the user to something besides dbo?
login properties screenshot
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Save solutions to your questions, answers you’ve discovered through searching plus helpful articles in your personal knowledgebase for easy future access.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.
Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Thank you. The explanation, in my words:
The login designated as database owner is implicitly mapped to the special user dbo and cannot be mapped to different user. So, if a Login is the designated owner of a Database, then the mapped user for that Database is unconditionally [dbo] and cannot be changed. Furthermore, that Login cannot be added as a User to the database.
Solution: change the database owner
Business Accounts
Answer for Membership
by: aaronakinPosted on 2008-06-08 at 12:41:42ID: 21739321
You need to change the dbo user to another login first...usually sa.
USE MAX_Struct
EXEC sp_changedbowner 'sa'
Then you can remap the OAK\dennis login to another db user.