When is the time to create a second database?

Question

I have a mysql database that has grown to over 200 tables. I know that this is not a performance issue, but most of the administration tools that I have are not organized enough to easily manage this number of tables, and I’m thinking about putting some (new) tables in a second database only for my own sanity.

Has anyone else taken this path, and was it worth it, or was it ultimately more of a problem than having one monolithic database?

Edit: Thanks for all the answers, although I was looking for some real experience, not hypothetical advice, sorry, I can not choose the correct answer.

Answer 1

I think you have a problem with the tool, not a problem with the database! Then my advice would be to change your tools, rather than breaking your database into several parts. A short-term “advantage” (with a shorter list of tables) will lead you to several long-term problems, such as managing code to update / retrieve data between multiple databases.

Answer 2

, , . , . , , , , , , , , .

Answer 3

, . , , .

Answer 4

, . , . - , . , .

Answer 5

600 , . MySQL Query Browser MySQL Administrator , - ?

Answer 6

- , .

, .. 2 , ( , ..)

Answer 7

200 ? , .

, , , ( ..), . , , ?

Answer 8

, . , , , . "" .

Then my database list will look something like this: project1
project2
project3
link