In which case should you use different Databases? [closed]

Question

In which case should you use different Databases? [closed]

Navigation

#1 by (-1 votes)

-2

In the company we currently have 3 applications which perform totally different functionalities, in some cases these applications share information such as (Users, Companies, Products, etc.). Currently these applications have independent databases, and the integrations are made through Web services, the support team has proposed to have a single database to facilitate the installation process of the three systems, I do not see a technical or reason why it can not be done. The question is: When should you choose to have separate databases? It is a good practice to have a single database for different systems, what should be taken into account when defining this?

Thanks

asked by Juan Diego Calderon Henao 29.03.2017 в 16:55

source

1 answer

Load data in specific columns Select does not catch the correct value of the TextField when modifying it

score -1 · Accepted Answer

I do not think it's good to have tables of different applications in the same Database, if only by common sense. Then strange things happen to me that could happen as that making a backup and a restoration of a Database for an application, represents that I would be restoring the data of the three applications, since they share the same Database.

You do not comment on the DBMS you are using, but some of them allow you to consult between different databases, therefore, in your case, you would choose to have the common tables in a main database (of the three) and in the others no, or failing that if it is not possible, to have a SISTEMA Database, and then one for each application.

If you need to install 1 application always install the SYSTEM and the specific application. If there are 2, the one of SYSTEM and the two of the applications.