|
|
|||||||||
|
|||||||||
| |||||||||
|
|
|
| |||||||||
![]() |
|
|
«
Previous Thread
|
Next Thread
»
|
Thread Tools | Search this Thread | Rate Thread | Display Modes |
|
#1
|
|||
|
|||
|
We are using 8i and was wondering if there is a limitation as to how many columns can there be in a view. Also from a design and performance perspective is it acceptable to have views with 100+ columns ? any help will be highly appreciated.
jiggaman |
|
#2
|
|||
|
|||
|
I think the 255 columns limit still applies for 8i.
The view's performance is under the influence of several factors: 1. SQL in the view text 2. How the optimizer (plus hints) responds to the text. If you execute the sql for the view with EXPLAIN PLAN, it will tell you good/bad performance. 3. How well the indexes, etc., are set up for the underlying tables. I'm personally not a fan of database designs that have tables and views with huge numbers of columns. It usually indicates a really bad design. A view should try really hard to serve ONE business requirement and do the job perfectly. It shouldn't try to answer all possible situations. |
|
#3
|
|||
|
|||
|
Thanx for the reply. Personally I avoid creating such big views, however the information that is captured the table itself i ihas 100+ fields. so now we go to heart of the problem that the table itself have many fields, we could store redundant column info in one colum and the actual data pertaining to that in another column, there by reducing the no of colums. but now there is just to much redundant data in the table. any suggestions ?
|
![]() |
| Viewing: Dev Shed Forums > Databases > Oracle Development > View Limitations |
| Thread Tools | Search this Thread |
| Display Modes | Rate This Thread |
|
|
|
|