Re: Number of Columns in a table.

From: DA Morgan <damorgan_at_psoug.org>
Date: Sat, 04 Mar 2006 13:10:25 -0800
Message-ID: <1141506615.561675@jetspin.drizzle.com>

Thomas Kellerer wrote:
> DA Morgan wrote on 04.03.2006 00:43:
>

>>> I would have loved to do that. This increases my storage requirements
>>> by 5 times.
>>>
>>>> From 5 Tera bytes to 25 Terabytes and makes my queries more complex .
>>
>>
>> Not possible: Bytes are bytes are bytes. Whether stored horizontally
>> or vertically. Even on Teradata.
>>

>
> Of course, bytes are bytes. But you will need more of them if you move
> to a vertical structure. With the name/value approach you'll store the
> name each time as well,

Why would you do that? I can understand storing an INTEGER but storing the name? Defeats the point of a relational design.

SQL> select vsize(testcol), testcol from t;

VSIZE(TESTCOL) TESTCOL
-------------- ----------

3 999

Three bytes per record equals 999 columns.

-- 
Daniel A. Morgan
http://www.psoug.org
damorgan_at_x.washington.edu
(replace x with u to respond)

Received on Sat Mar 04 2006 - 15:10:25 CST