[prev in list] [next in list] [prev in thread] [next in thread] 

List:       postgresql-general
Subject:    Re: [GENERAL] Postgres Design
From:       "Jim C. Nasby" <decibel () decibel ! org>
Date:       2004-11-30 23:15:34
Message-ID: 20041130231534.GP41545 () decibel ! org
[Download RAW message or body]

Speaking in a general sense, it's almost never a good idea to split
something across databases by an arbitrary boundary such as year. It's
also not a good idea to split things into multiple databases across
logical boundaries unless there's a compelling reason to do so.

On Tue, Nov 30, 2004 at 02:27:32PM -0500, Morris N. Grajower wrote:
> I have hundreds of different survey files in a customized database.
> I would like to convert them to postgres.
> My question is should I create one database for all the surveys or 
> should I limit the number of surveys to a database.
> for example create a different database for each survey year, or by 
> research company ?
> 
> 
> ---------------------------(end of broadcast)---------------------------
> TIP 3: if posting/reading through Usenet, please send an appropriate
>      subscribe-nomail command to majordomo@postgresql.org so that your
>      message can get through to the mailing list cleanly
> 

-- 
Jim C. Nasby, Database Consultant               decibel@decibel.org 
Give your computer some brain candy! www.distributed.net Team #1828

Windows: "Where do you want to go today?"
Linux: "Where do you want to go tomorrow?"
FreeBSD: "Are you guys coming, or what?"

---------------------------(end of broadcast)---------------------------
TIP 6: Have you searched our list archives?

               http://archives.postgresql.org
[prev in list] [next in list] [prev in thread] [next in thread]