tags:

views:

10

answers:

0
Q: 

Are there any pitfalls with having multiple MySQL databases on 1 server node?

I want to prepare my database for sharding in the future. But right now I only need 1 node.

What I'd like to do is to shard the database into virtual shards, say 12 shards, and put all of them onto the same server node for now.

And when I need to scale out, I could just then get a 2nd server and move 6 of the 12 virtual shard onto the new machines.

Are there any pitfalls with having 12 different databases on 1 machine?

  • Can I still run only 1 MySQL instance to support those 12 databases?
  • Does having 12 databases result in higher memory usage?
  • Does this require having 12X as many database connections?
  • Any other pitfalls?

Thanks.

related questions

Remove Quotes and Commas from a String in MySQL
What's the best way of converting a mysql database to a sqlite one?
How do you manage databases in development, test, and production?
Multiple foreign keys?
Add 1 to a field (MySQL)
Issues using MS Access as a front-end to a MySQL database back-end?
Bigger than a char but smaller than a blob
How do I retrieve my MySQL username and password?
Long-time LAMP Developer moving to VB.NET
How do I Concatenate entire result sets in MySQL?
Full complete MySQL database replication? Ideas? What do people do?
SQL: Distribution of table in time
SQLite vs MySQL
How do I create a new Ruby on Rails application using MySQL instead of SQLite?
Multiple Updates in MySQL
MySQL/Apache Error in PHP MySQL query
What all do I need to escape when sending a (My)SQL query?
Auto Generate Database Diagram MySQL
Mechanisms for tracking DB schema changes
How big can a MySQL database get before performance starts to degrade.
Python and MySQL
SQL Server 2005 implementation of MySQL REPLACE INTO?
How to export data from SQL Server 2005 to MySQL
Throw Error In MySQL Trigger
Binary Data in MySQL