I am currently working on an online building materials application. Companies can register on our website, and then they can use webapp.
From the very beginning, the idea was to create a database for each client. But now it’s getting bigger and bigger (100+), so we have 100 databases to manage.
We need to run approx. twice a year update script for db maintenance.
The advantage that I see is that when the client wants to exit, we delete our database and end it.
When I want to add a new client, I have to populate the database with approx. 1,000,000 unique records for this particular customer, because each customer has different prices / materials.
For backups, I use the MySQL Dump script, which creates a * .sql file for each database that I load every day.
What is your opinion and what do you think? One big db or client database?
I am using MySQL with ASP.NET/C # ...
source
share