Jeff,

I vote for different databases for each customer, even if it sounds like a
lot. For programs, it's just swapping pointers when the database is
connected for the application, so programming internals shouldn't change
(for the most part).

I'd do this for the safety factor alone. I don't think the server is going
to be hurt by some extra folders, and if you have that many customers - good
for you and you can afford a bunch of servers :)

Also I'll mention that I use a system of "profiles" (tables) for entities
such as customers, databases and tables (et al) that's used for
organizational metadata with pointers to actual files. It took a while to
work it all out, but it's settled down and maintained through the tables.
Saying this because this scheme wouldn't work if databases or tables contain
data for more then 1 customer.

Another complication would be customers wanting copies of their database
backups.


Bill

> -----Original Message-----
> From: [email protected] 
> [mailto:[email protected]] On Behalf Of Jeff Johnson
> Sent: Wednesday, February 17, 2010 6:39 PM
> To: [email protected]
> Subject: Database Design Question
> 
> 
> Looking for opinions here.  Most of my customers have several sites. 
> With VFP I always put different sites in different folders so 
> each site 
> has identical databases.  When considering SQL Server or PostGreSQL 
> multiple databases seems cumbersome.  The other option is to have one 
> database with one set of tables and have a site field.  The 
> problem with 
> this approach is that there is a chance that a mistake could make one 
> site's data available to another site.  There is a lot of 
> overhead for 
> printing reports and accessing data to keep thing separate.
> 
> Can anyone conger up pros and cons for the two approaches?
> 
> -- 
> Jeff
> 
> Jeff Johnson
> [email protected]
> SanDC, Inc.
> 623-582-0323
> Fax 623-869-0675
> 
> 
> 
[excessive quoting removed by server]

_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/profox
OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: 
http://leafe.com/archives/byMID/profox/6b9c67b1849449e5a105b4dad8f96...@bills
** All postings, unless explicitly stated otherwise, are the opinions of the 
author, and do not constitute legal or medical advice. This statement is added 
to the messages for those lawyers who are too stupid to see the obvious.

Reply via email to