Purpose of owning a schema in SQL Server I've been spending the last few days cleaning up database permissions, grouping them all into AD groups and removing orphaned users.

This has lead me to a recurring scenario:


Find a user that owns a schema
Transfer schema ownership to SA
Remove user


The schema's are not subject to regular change, and most of the time it's a user owning the dbo schema.

I've been researching what the reasoning might be behind giving these users ownership of schema s, however I can't really find a proper reason. Most documentation speaks of schema membership, using schema's for permissions, but I'm hard pressed finding much about schema ownership.

What might be a correct reason for giving users ownership of schema's?
Are there any hidden dangers in removing schema ownership from orphaned users?
An owner of a database object has full rights on it automatically and unrevokably. But of course you can give an user all rights to a schema without making him the owner.