Re: split up tables or one big one?

it all depends on what the data is and how you are going to use it ... if
its going to result in this major JOIN to get results, or several queries,
you are best with teh multi-GB table ...

On Sat, 26 Aug 2000, Patrick Goodwill wrote:

> Hi!
>
> I'm writing a system which i could logically separate it into hundreds,
> perhaps thousands, of tables, or it could put it all into one big table.
> Since each tables could probably only grow to 10s of MBs in size, from a
> design, speed, and scalability perspective, is it perferable to split up
> the tables (as I've currently programmed it) or to put everything into one
> gigantic, multi-GB table?  This is for the web, so transaction speed is
> important.
>
> Patrick.
>

Marc G. Fournier                   ICQ#7615664               IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: scrappy@hub.org           secondary: scrappy@{freebsd|postgresql}.org