Timeline for Multiple databases or one single database
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 15, 2017 at 22:20 | vote | accept | QConscious | ||
| Jan 15, 2017 at 14:32 | comment | added | Erik Hart | Splitting relational databases is a really difficult topic and should really not be done just for alleged performance gains - which will in part be spoiled by synchronization efforts. And it's completely useless on the floating mainframe in the sky (aka cloud), where there is no actual control over the physical locations. | |
| Jan 15, 2017 at 11:53 | comment | added | QConscious | Basically all of it is going to be structured, and I plan on using SQL for it. I think I may just be overthinking it like the person who commented suggested. I was thinking it would be more efficient to have 3 sql databases with less tables int hem all. But there doesn't seem to be much of a reason for that | |
| Jan 15, 2017 at 11:40 | history | answered | Erik Hart | CC BY-SA 3.0 |