I don’t know what you mean by integrating into one database. Do you mean changing three projects into a common database, or do you mean putting three databases on one machine? If it’s the former, I don’t feel good about it, because since there are three projects, the databases should be separated. Putting them in one database will cause conflicts in table names, etc., and it will be very troublesome to modify. If it is the latter, I don’t know if each of your projects is in the form of 1 master and n slaves. If so, you can first use a slave machine to merge the three data slaves together, and then perform the master From the switch, when switching the main database to the merged machine, the configuration differences of each previous server must also be taken into consideration.
I don’t know what you mean by integrating into one database. Do you mean changing three projects into a common database, or do you mean putting three databases on one machine?
If it’s the former, I don’t feel good about it, because since there are three projects, the databases should be separated. Putting them in one database will cause conflicts in table names, etc., and it will be very troublesome to modify.
If it is the latter, I don’t know if each of your projects is in the form of 1 master and n slaves. If so, you can first use a slave machine to merge the three data slaves together, and then perform the master From the switch, when switching the main database to the merged machine, the configuration differences of each previous server must also be taken into consideration.
Program integration, triggers, stored procedures, foreign keys, whatever you want
The answer still needs research