I am managing a database design project.
It will database our entire website including:
images, articles, bibliography, ecommerce, membership in website, site
The 'lumper' team member says "let's make it all one giant database with
dozens and dozens of tables".
The 'splitter' team member says "let's make it many separate databases each
having fewer tables".
What are the advantages and disadvantages to 'lumping' all tables into one
database vs. 'splitting' into multiple databases with fewer tables?
Stay informed about the latest changes at masks.org,
sign up for the eNewsletter at:
masks.org survives on your donations.
Please help by mailing a tax-deductible donation to:
P.O. Box 12089
Olympia WA 98508
Our website is at:
pgsql-novice by date
|Next:||From: Alfred Perlstein||Date: 2001-02-07 02:00:47|
|Subject: Re: When do you separate databases?|
|Previous:||From: Tatsuo Ishii||Date: 2001-02-07 01:12:58|
|Subject: Re: Re: [NOVICE] Re: Sizing of LARGE databases.|