Josh Nathanson wrote: > Rick, the only thing I'm wondering is, why create a separate database for > each client's site data. That seems to add a layer of complication that > might not be needed.
Security, Backup/restore, code complexity, site portability. Multiple commercial clients on multiple web sites - even all on one server.. I want each of them to have their own database, their own datasource, etc. That's the security. If one client messes up his data in a massive way, it's a lot easier to restore HIS database and not worry about the other clients. Having to add a client ID to every method call - or at least to every query - adds a level of code complexity *AND* data complexity that simply isn't necessary. Site portability - most of the time, I build sites for my clients, and they own the sites - and the code. Even if I'm reusing my own code and giving them a discounted rate cuz I don't have to redevelop, they can still take their web site to another developer, another hosting company, etc. Unless you're building a massive production system where the benefits of having a single database outweigh the above issues.. I think it's a much better idea to have separate databases. Rick ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Introducing the Fusion Authority Quarterly Update. 80 pages of hard-hitting, up-to-date ColdFusion information by your peers, delivered to your door four times a year. http://www.fusionauthority.com/quarterly Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:262546 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4