When to use multiple databases vs multiple tables
<p>So I've been working on a project where I have lots of data. In some collections of data, there are parts of data that link to other collections of data as in relational databases.</p>

<p>However, I am confused over whether I should use multiple databases or multiple tables. I've tried to find out, and <a href="https://www.quora.com/What-is-the-difference-between-database-and-table" rel="noreferrer">answers from Quora</a> helped - from what I understand, if I have collections of data that link together, I should use one database containing multiple tables (these tables would link together).</p>

<p>If my understanding is correct, then how far is this practice appropriate? For example, would it still be okay if you had over 20 tables in one database? Would you use one </p>

<p>Also, when would you use different databases if you can put everything in one database containing multiple tables?</p>

<p>I hope this question isn't too vague or anything, but I could not find clear answers that explain the purposes of each and therefore why you would use multiple databases over multiple tables or vice versa.</p>