Schema - Do you avoid using user-schema separation?
  v4.0 Posted at 3/01/2020 4:21 PM by Christian Morford-Waite

​​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.​

​Figure: Bad Example - AdventureWorks using user schema - instead, keep it simple and avoid using user schema unnecessarily
Figure: Good Example -​ Adventure works with user schema cleaned out. Much simpler and more readable​​

Related rules

    Do you feel this rule needs an update?

    If you want to be notified when this rule is updated, please enter your email address: