0
Hello, Guys!
A company hired me to unify (and remake) several systems they own.
The job is to create single administrative panel for various sectors and products.
When thinking about data storage, I came across the following question:
I create a single database for all systems or a database for each system?
What is recommended? What are the best practices currently? Which consumes the least processing?
Thanks for your help!
3
The ideal would be to work with independent but unified databases through relational database normalization.
Each sector would be an independent base and each base would work with the related products. If necessary, the separate bases can be linked through the entity-relationship model, where the information from one base can be consulted in others, thus making its base more secure, because the information would be "dismembered", but without causing impact. Another advantage is that the access time would be significantly reduced, as the page would access a smaller base, and, if necessary, use its relational fields to directly access information from other databases.
In my company, we have worked with this model of related bases since 2008, and the production gain is very high.
If you want more information, I leave a link that my college professor left us for further reading.
http://www.dsc.ufcg.edu.br/~pet/jornal/maio2011/materias/Recapitulando.html
Thank you so much for the tip!
Browser other questions tagged php mysql
You are not signed in. Login or sign up in order to post.
Without knowing the most detailed details of your requirements, the answer to each of your inquiries is "depends on". Now, if I had to bet, a database for each system tends to be more organized - but again, this depends on of its definition of "system".
– Oralista de Sistemas