sql server error "The database principal owns a schema in the database, and cannot be dropped."

In SQL Server 2005, if you try to drop a database user by right-clicking the user name and clicking Delete, you may encounter an error as follows.
"The database principal owns a schema in the database, and cannot be dropped. (Microsoft SQL Server, Error: 15138).

This problem normally occurs when a user owns a schema and you are trying to delete the user.
There are many workarounds for these one is

Using the GUI in "Object Explorer" (MS SQL Management Studio) Expand the [databasename] / Security.
Click on Schemas.
In summary window, determine which Schema(s) are owned by the user and either change the owner or remove the Scheme(s).
The user can then be deleted.

Or using AdventureWorks DB you can for example:-

USE AdventureWorks;
GO
ALTER SCHEMA HumanResources TRANSFER Person.Address;
Go

And HAPPY GO LUCKY

New on Geeks with Blogs

We Won The One Award I Actually Care About

Full Scale made the Inc. 5000 for the fifth year straight, the 12th listing across my three companies. Here is why the one award you cannot buy is worth stopping for.

Your Customers Build the Features Now

I let a tool I liked sit dead for a year rather than build the features I wanted. An MCP server meant I never had to, and your customers can do the same to your product.

Get the Size of a Directory in Linux the Easy Way

du -sh for the quick answer, ncdu for the cleanup, df for the disk itself: every command for checking directory size in Linux, plus why du and df never agree.

Vim Search and Replace: The Ultimate Guide

One :%s command replaces every match in a file before a find dialog would even open. The Vim substitute patterns worth the muscle memory: flags, ranges, capture groups, and multi-file edits.