Tag Info

New answers tagged

0

See my answer to this question which is similar in scope to your own question, except that your project is already up and running, so you can ignore the recommendation to use PostgreSQL instead of MySQL if starting from scratch. As Lmu92 points out, the one thing that is critical in a scenario like this is to have a very clear set of procedures about ...


0

You should store all information that is common for all companies in one database and copy the data that are needed to the database that needs the information. Adding a new customer would be done in the common db. After that the information will be copied to company1. If it's needed in company2, then the data will be copied to company2. Make sure you also ...


0

There is no way, there is only the journey! You could start here with MySQLTuner - it's a tuning script which issues recommendations - it doesn't modify anything on the server and I have read (can't find ref, sorry) that it's impact on performance while running is minimal. There's also this - but it seems to be dead. I'll just repeat the warning that comes ...



Top 50 recent answers are included