title: Multiple database in EF6
body: <p>We are involved in quite a new development in which we are remaking our current web shop platform.
  In the current platform we do not use EF6 neither other ORM but store procedures to access to the db, but in the new building is what we do.</p>
  
  <p>We have a doubt regarding database design of the new platform. In the current platform we use several different databases depending on the content of them.
  For example, we have dedicated databases to store information for products catalogs other dedicated db for handling orders. 
  Currently all data access is done through stored procedures, so we have no problem with the links between different databases.
  The problem appears to us now when we have started to use EF6. In this case each DB is associated with a context and it is not possible to know data from one context to another 
  unless we implement directly in the source code these relationships using various contexts. It looks like these means we will lose the power of EF6.</p>
  
  <p>The questions we have are:
  Is it a bad design maintaining different databases for the same application using EF6?
  in case this is a poor design and choosing for a single database, is the performance going to be optimum even driving hundreds of tables (almost 1000) with several TBytes of information?
  in the other hand, in the case of opting for the design in which several bbdd appear (it would be much better in our case), what is the best way to handle them EF6?</p>
  
  <p>Thank you very much for your help!</p>