title: Using SQL tables with the same name on different schemas
body: <p>Does anyone know of available white papers discussing the use of tables with the same name existing on different schemas?</p>
  
  <p>I'm implementing on SQL Server but I imagine the theory can be applied to any RDBMS.</p>
  
  <p>To be a little more specific, say I have a db that serves two applications and there's some crossover of resources between applications but some datasets are stored on separate schemas.</p>
  
  <p>For example</p>
  
  <pre><code>App1.tblSomeData
  
  App2.tblSomeData
  </code></pre>
  
  <p>What are the advantages/disadvantages of using the same name for both tables? The other alternative is to use different names:</p>
  
  <pre><code>App1.tblSomeDataForApp1
  
  App2.tblSomeDataForApp2
  </code></pre>
  
  <p>This insures that all table names are unique, but does this have advantages/disadvantages?</p>