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?
Start Free Trial