Database structuring formulation help!

[kurokotoque]

---

ano po ang mai-suggest niyo sa ganitong scenario:

isang company na may maraming branch.since isa lang sila, dba sa structuring ng bawat isa ay magkapareho lang at sa mga data lang sila nagka-iba.

im confused kung ano ba dapat ang design..
should i create an individual database each of this branches pero ang problema, lalaki masyado ang storage at magkakaproblema sa updating of structure since iisa lang ang system flow ng bawat isa or

make a single database and have a table for each branches pero ang problema nman dahil sa dami ng branches at sa mga magiging entries nila,baka magkakaroon ng crash in the later part..

pls.... help me with this one guys...thanks

[moz_k2]

the problem if you use centralized db for all the branch is
when the server on the main branch is down.
all the branches is frozen. no transactions can be processed.
imagine the loss incurred of its unavailability for 1-2 hours.

My solution would be to put a database for every branch.
Then a central server where you will upload the data from every branch periodically.
And design your software that allows it to access remote(i.e. main, other branch) database if ever local db is not available.
For the central db you might want to apply clustering.

hope that helps

[javapenguin]

Try to check database replication, there are many kinds of replication depending on your RDMS. You might want to considered certain types of RAID to avoid crashes.

[TheGame!]

@moz_k2 good solution...

@moz_k2 is talking about data synchronization functionality, so if the main database server is down.. you could save also your data from local machine or solo database and sync later on as soon as the main database server is up...

[Tin_Tin]

how often pud i upload sa central server ang data gikan sa mga branch servers...?