Home > Archive > MS SQL Server > February 2006 > Best Practices for Schema in SQL Server 2005 after upgrading?









You are viewing an archived Text-only version of the thread. To view this thread in it's original format and/or if you want to reply to this thread please [click here]

 

Author Best Practices for Schema in SQL Server 2005 after upgrading?
SteveM

2006-02-16, 9:23 am

Is there a best practices guide for schema management? Is it best to
remove objects from dbo?

My understanding is that upgrading a SQL Server 2000 database will
result in all objects being moved into a dbo schema.

However, I've read some posts here that this setup isn't necessarily
the best practice for establishing schemas. We would also like to
eliminate the need for database - level dbo's.

So, I'm thinking that once a database is converted, that I would create
a new schema "prod" and then create a schemaowners role. The old dbo's
would then be made members of that role and then removed from the old
dbo role.

I see that then I can alter a schema and transfer the dbo objects. Is
this done only at the catalog level and doesn't actually cause a
movement of data?

Once the objects are moved, permissions would be recreated and users
would have the new schema made their default schema.

Seems the only issue at this point should be any code explicitly
referring to dbo objects (i.e, "select * from dbo.xxxx).

Any issues with this? Or, not really necessary?

Sponsored Links





Also available: Server administration forum archive | Web Design forum archive | Software forum archive | Hardware reviews archive | Programming forum archive

Copyright 2009 droptable.com