Re: Too many columns (rows) in a table

I would probably break it up one more:
[products table]
products_id
product description

[language table]
language_id
language description

[description table]
product_id
language_id
description_id
description_text

Don't sweat the 30 million rows. You're not the first person to have a big table. In fact, if your descriptions are short, you might have indexes larger than you description table.

--rn.

--

<caramel98_at_my-deja.com> wrote in message news:86eg5g$91s$1_at_nnrp1.deja.com...
> Hi,
>
> I have to create a table for the following:
> - 100 000 products
> - each product has 10 descriptions
> - each description must be in 30 languages
>
> If I create one table to contain all of the properties of the products,
> I'll have at least PRODUCT_ID + 30*10 = 301 columns.
>
> An other choice can be to use two tables:
> - table PRODUCTS with PRODUCT_ID and other columns
> - table DESCRIPTIONS with the columns
> - PRODUCT_ID
> - DESCRIPTION_ID
> - DESCRIPTION_LANGUAGE
> - DESCRIPTION
>
> The table DESCRIPTIONS will contain 100 000*10*30 = 30 000 000 rows
>
> Is there a best way ?
>
> Thanks for any help.
>
>
> Sent via Deja.com http://www.deja.com/
> Before you buy.
Received on Sun Jan 23 2000 - 11:02:21 CST