Schema - Do you avoid using user-schema separation?

Last updated by Brady Stroud [SSW] about 1 month ago.See history

User-schema separation allows more flexibility by adding another level of naming and shifting ownership of database objects to the schema, not the user. So, is it worth doing? Unless you are working with a very large database (100+ tables), the answer is "no". Most smaller databases have all objects with owner "dbo", which is fine in most cases.

SQLDatabases UserSchema Bad
Figure: Bad Example - AdventureWorks using user schema - instead, keep it simple and avoid using user schema unnecessarily

SQLDatabases UserSchema Good
Figure: Good Example - Adventure works with user schema cleaned out. Much simpler and more readable

Adam Cogan
We open source. Powered by GitHub