In our SQL Server 2000 we have a windows group which has dbo permissions (db_owner) on a certain database. When a member of this group creates a stored procedure it is owned by the person who created the stored procedure. (This is not what we want) on the other hand when he creates a new table it is owned by DBO
The disadvantage of objects NOT owned by dbo the application needs to prefix the owner in the code. It also becomes a mess when more then one person is able to create stored procedures in the database.
Can anyone explain this behaviour and tell if I can do anything about it.