Guidance about developing a public application with lots of db's

[eluser]kevinprince[/eluser]
Hey,

In theory that works, however were not just dealing with client data, there is also going to be ledgers, products, and event records. This means as the application expands, i could end up with 1000s of tables in a single db (obviously i would be doing some sort of splitting ie 10 clients to a single db).


The problem remains the same...