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:
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 da
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