68 reputation
15
bio website
location Adelaide, Australia
age 37
visits member for 4 years, 4 months
seen Aug 5 '10 at 7:06

Web Applications Developer with skills in PHP, MySQL, HTML and JS.


Sep
24
awarded  Autobiographer
Nov
6
awarded  Notable Question
Dec
5
awarded  Popular Question
Jul
31
awarded  Nice Question
Jul
26
comment Single V/s Multiple Databases
I sure didn't think of this approach. This seems quite workable, but then again what limits this is the complexity factor while scaling. Given I'd have at-least 18 tables per client, a 20-client setup would mean 360 tables in the database to begin with. And if we reach anywhere near our sales projections, managing an 1800 table database would be painful. Comparatively, it would be better to manage 100 databases with 18 tables each. Thanks for your comments.
Jul
25
comment Single V/s Multiple Databases
Thanks mate, appreciate your help. I do agree that it boils down to tackling any such issue with a disciplined approach and keeping a strict check on how the system is extended.
Jul
25
awarded  Scholar
Jul
25
comment Single V/s Multiple Databases
Thanks @Tim and @Chris, your insights have been helpful.
Jul
25
accepted Single V/s Multiple Databases
Jul
25
comment Single V/s Multiple Databases
Thanks for the heads up guys.
Jul
23
awarded  Student
Jul
23
asked Single V/s Multiple Databases