Max Tables & Design Pattern

Question

I am working on an app right now which has the potential to grow quite large. The whole application runs through a single domain, with customers being given sub-domains, wh

Answer 1

Single Database Pros

• One database to maintain. One database to rule them all, and in the darkness - bind them...
• One connection string
• Can use Clustering

Separate Database per Customer Pros

• Support for customization on per customer basis
• Security: No chance of customers seeing each others data

Conclusion

The separate database approach would be valid if you plan to support customer customization. Otherwise, I don't see the security as a big issue - if someone gets the db credentials, do you really think they won't see what other databases are on that server?