Re: Any issues with large database views?

There is no rule which says that you have to store all of the data in one table.

You can break a record up into multiple parts, each using the same value for it's primary key, then
join (on each table's primary key) the tables when needed.

<clapoint149_at_my-deja.com> wrote in message news:7vkbt4$4ua$1_at_nnrp1.deja.com...
> Hello,
>
> I have the need to store records which will consist of several
> hundred but < 1000 fields. My current understanding is that for Oracle
> 8 and above the table column limit is 1000 and for previous versions of
> Oracle's database server the table column limit is 254. However, I
> have heard that even with the newer versions of the database server
> there are still issues with creating/using tables with more than 254
> columns. I personally do not know what these issues might be, nor do I
> know if they actually translate as problems per se. What I am
> wondering, though, is if these issues (whatever they are) also apply to
> large views (with several hundred columns) that join medium-sized
> tables (each with at most about 100 columns), which is how I prefer to
> store/access my large records. My guess is that large views are immune
> since any table problems most likely stem from physical storage design,
> but I do not know for sure. Could someone shed some light on any
> issues related to large database tables and views? Thanks.
>
>
> Cary
>
>
> Sent via Deja.com http://www.deja.com/
> Before you buy.
Received on Mon Nov 01 1999 - 12:35:06 CST