Re: Oracle performance - Table with 480 fields

Hi,

Better normalize that table.Try to establish master detail relationship by choosing proper keys. I think ( I am not sure ) oracle table supports maximum of 255 columns per table. If U dont have an option, consult with your DBA to choose larger oracle blocksize ( 32K or 64 K ) so that row chaining/migration can be avoided.

Mohamed Buhari
Oracle DBA

Melissa Star wrote:

> Hi everyone,
>
> Do you know if a table with 480 fields will perform well, and whether it
>
> will cause a significant performance difference compared to an ordinary
> table with 20-30 fields?
>
> The table in questions needs to store time-related curve data,
> basically, five minute readings over a 24 hour interval.
>
> If the performance is not going to be acceptable with 480 columns, what
> would be the best solution to store the curve data?
>
> * A one to many relationship or design in which an entire 24 hours is
> not contained in one row may be impossibly slow, since the table will be
>
> accessed VERY frequently
>
> * Using Oracle 8i's array type?
>
> * Storing the full 24 hours of data at a BLOB and manipulating it
> oustide of Oracle only?
>
> Thanks everyone,
>
> Melissa Star
Received on Mon Jan 24 2000 - 18:37:16 CST