It just adds another level of performance on large databases esp when the load is uneven.
"This e-mail is from Reed Exhibitions (Gateway House, 28 The Quadrant, Richmond, Surrey, TW9 1DN, United Kingdom), a division of Reed Business, Registered in England, Number 678540. It contains information which is confidential and may also be privileged. It is for the exclusive use of the intended recipient(s). If you are not the intended recipient(s) please note that any form of distribution, copying or use of this communication or the information in it is strictly prohibited and may be unlawful. If you have received this communication in error please return it to the sender or call our switchboard on +44 (0) 20 89107910. The opinions expressed within this communication are not necessarily those expressed by Reed Exhibitions." Visit our website at http://www.reedexpo.com -----Original Message----- From: Rick Faircloth To: CF-Talk Sent: Sat Dec 02 02:13:12 2006 Subject: RE: Advice needed on how to proceed with app... > 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. Maybe I'm not quite seeing your vision clearly. Hi, Josh... No, you've got the vision straight... I'll reconsider the database approach. I think I'm just remembering the pain it was to deal with the database when it was handling *every* part of the site... all graphics, text... everything. That was overkill... Now that I'm creating the sites separately, it probably would be better to maintain client data in similar tables, using Primary & Foreign Keys to link the data to the site. I wonder if there's better database performance one way or the other? Seems like it would be quicker for a database to parse through data for only one site, rather than for any number of sites... but it certainly would be easier on me to create the db just once... probably go that route... Thanks for the feedback, Josh. Rick -----Original Message----- From: Josh Nathanson [mailto:[EMAIL PROTECTED] Sent: Friday, December 01, 2006 5:24 PM To: CF-Talk Subject: Re: Advice needed on how to proceed with app... 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. Maybe I'm not quite seeing your vision clearly. You could have a Clients table to hold that information, including their domain name or whatever...then in your actual site data table, have a foreign key for the ClientID. This would achieve the separation you're looking for, without having to worry about managing separate databases. So you'd have: Client Table ClientID (primary Key), Name, Domain, Address etc. SitePages Table ClientID (foreign Key), SitePageID (primary Key), PageContent etc. Listings Table (this is for Real Estate right?) ClientID (foreign Key), ListingID (primary Key), Address, SqFt, Price, Bedrooms etc. This would all be in a single database, and would be easier to maintain than creating separate databases for each client. -- Josh ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| 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:262579 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4
