title: SQL Server: conventions for naming a schema
body: <p>Consider a database server whose job today is to house one database. Likely the database will be moved in the future to another database instance which houses multiple databases &amp; schemas.</p>
  
  <p>Let's pretend the app/project is called Invoicer 2.0. The database is called AcmeInvoice. The database holds all the invoice, customer, and product information. Here's a diagram of the actors and their roles and behaviour.</p>
  
  <p><img src="https://i.imgur.com/qwHrY.png" alt="alt text"></p>
  
  <p>The schema(s) will largely be used to easily assign permissions to roles. The added benefit here is that the objects aren't under <code>dbo</code>, and that the objects &amp; permissions can be ported to another machine in the future.</p>
  
  <p><strong>Question</strong></p>
  
  <ul>
  <li>What conventions do you use when <strong>naming</strong> the schema? </li>
  <li>Is it good form to name the schema the same as the database?</li>
  </ul>