Re: DBA performance and modeling question

    I'm currently working on an ecommerce project and facing several tables that could potentially get very large. I've been urging people to think about whether they actually need 30 million active records or whether there is some reasonable basis on which we can take them out of the database after a certain time or after we know they're no longer relevant.

    Is this a possibility for you?

Van

"datasyst" <datasyst_at_ix.netcom.com> wrote in message news:3A155D08.A59DB77E_at_ix.netcom.com...
> I have a situation where we have exactly same table for different types
> of objects. The question is should we model it as multiple tables even
> though the columns are same or should we model it as one large table and
> have "type" as a column which distinguishes the records. The criteria
> we are evaluating is the table can become huge with e-commerce sites.
> We are assuming this table is going to be huge with 20-40million
> records. If we design it as multiple tables, there are 4 types, which
> could break down to 5 -10 million records per table if we keep them as
> separate tables.
>
> In terms of database design I like it as one table but not sure if
> having many small tables will be any performance benefit vs one big
> table. Most of the queries will be using index search.
>
> Thanks in advance.
> SRK
>
Received on Fri Nov 17 2000 - 12:39:47 CST