On Wed, Feb 17, 2010 at 6:38 PM, Jeff Johnson <[email protected]> wrote:
> When considering SQL Server or PostGreSQL > multiple databases seems cumbersome. There's little cost to multiple databases. In classic design, all transactions should be occurring within a single database. It's a lot cheaper to have many databases (and many tables) than to have to cobble up a bunch of code to separate out one type of record than another, code that will be overhead every time the app is run. Separate databases lets you configure specific user rights only to the data they should access, avoiding the possibility of cross-leakage you're concerned about. Pros: simpler and faster code Cons: more separate data to back up. -- Ted Roche Ted Roche & Associates, LLC http://www.tedroche.com _______________________________________________ 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/[email protected] ** 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.
