One database with a site_id is best for a hosting environment, each db connection requires overhead. However, I would suggest that you do both, as this would gain your portability as well.
Robert -----Original Message----- From: Dan Stein [mailto:[EMAIL PROTECTED] Sent: Monday, November 17, 2003 3:45 PM To: [EMAIL PROTECTED] Subject: Witango-Talk: Multiple DB vs. Site ID I am in the process of rebuilding an application so it can be resold to customers. In some cases customers will elect to have me manage the hosting which I will be contracting out. I could build one database and manage the data with one set of taf files and then pull data based on the site ID ( I expect this all to be relatively low volume sites with periodic burst of users but averaging 1000 to 5,000 members per customer. Or would it make more sense to create a new database for each customer and build the taf files so they were dynamic in terms of what database they hit and what look and feel they loaded. Seems like the later is best to me. I'm wondering what the list thinks. Dan -- Dan Stein Digital Software Solutions 799 Evergreen Circle Telford PA 18969 Land: 215-799-0192 Mobile: 610-256-2843 Fax 413-410-9682 FMP, WiTango, EDI,SQL 2000 [EMAIL PROTECTED] www.dss-db.com "When you are born, you cry and those who love you rejoice. And if you live your life as you should, when you die, you rejoice and those who love you cry." ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/maillist.taf ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/maillist.taf
