Dropping Database role Schemas

  • Starting the process of figuring out how will use schemas in 2008 (we skipped 2005).

    Does any one know if there is a down side to dropping the schemas that match database system roles (eg db_owner schema)?

    David

  • If there are no objects in the schema, drop away.

    If you upgrade a database from SQL 2000 to 2005 or 2008 you can end up with some schemas that have nothing in them. Just drop them, they don't do anything.

  • Also, make sure you look up the right way to create a user, CREATE USER. A lot of our 2000 scripts were using sp_grantdbaccess, which will create a user, but will also create a schema for that user. If that does happen, you can just drop those schema's. They're not needed.

    "The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
    - Theodore Roosevelt

    Author of:
    SQL Server Execution Plans
    SQL Server Query Performance Tuning

Viewing 3 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic. Login to reply