Oracle performance - Table with 480 fields

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:26:59 CST