title: SQL 'multiple schemas on same DB' or 'multiple DB' on same server?
body: <p>i have an SQL database server with many tables most using the default schema <strong>dbo</strong>.TABLE and specific tables use something like <strong>Library</strong>.TABLE on the same Database, which is kinda of a way for me to know that these tables belong/being used by a Library system/application and the default schema 'dbo' ones contain generic data that can be used in any system that utilize this DB server. one reason it is like this is simple it was given to me like this.</p>
  
  <p>i have a plan to extend this database with more system tables which is somehow related to each other. (for example: 'Librarian time-sheet', 'borrowed books list', etc...) but i am wondering if i should keep using the same <strong>X</strong>.TABLE naming on the same DB or should i start creating more Databases on the same SQL instance?</p>
  
  <p>i did not finding any concrete answer for this but from what i can see from an App developer side it would be easier to check which system use which DB and tables instead of putting all in one. i assume that if i create more DBs i can later (if needed) start moving DBs to difference SQL instance or different servers entirely more easily.</p>
  
  <p>should i go with <strong>X</strong>.TABLE format or create new DB for each App Table Set assuming i have only one server to work with?</p>
  
  <p>EDIT: i am using MySQL actually but i am not familiar what it is called here i inferred the naming from Oracle</p>
  
  <p>*in response to "Prachi Thakkar" Sorry for the confusion. i meant new DB for each "group" of tables related to a system</p>