Suggestions On Table design - Usage of Nested Tables.

Question

Hi All,
DB Vesion - 10.2.0.1.0
We have an existingtable say, REPORT_MASTER with more than 4 Million records.( 27 Columns )
Now the requirement is as follows: Every day, a job has to run to upadte each row in the REPORT_MASTER table. ( COLUMNs to be updated are new columns -to be designed)
Rules for the updation are generated dynamically depending on a parameter table.
In total, more than 500 update statement will run for updating the whole table (it is not possible reduce the number of updations). Now after the updation the records in the table will be like
ExistingColumns     NewColumn1     NewColumn2     NewColumn3     ........
........     BRF01.1          BRF02.5          BRF03.1          .......
........     BRF01.3          BRF02.1          BRF03.2          .......
........     ......          ......          ......          ......First few updates, for example will update "NewColumn1". Next few updates will update "NewColumn2" and so on..
Now My Query is about designing the new columns:
1.If I did as the above sample output there should be 37 new columns as per current requiremnent. It can increase when new report is required.
2.If I go for a Nested Table, my concern is about the update statement. Is there any way to achieve the below code..
      update report_master
     set new_nested_tab_col(5) =  'BRF02.6'
     where .....
    And also how will be the performance?
3.If I go for a detail table, it will have a size of almost 37 times that of master_table.
I have to loop through this table (ofcourse with joining to the master table) 37 times again afetr updation for report generation. (This is required anyhow, but here data volume is high)
4. Other methode, ofcourse not very professional, is to keep a single varchar2 column and update that column, so that it will have value like
BRF01.1,BRF02.3,BRF03.1....
Or any other better alternative..?
Please suggest.
Thanks in advance,
Jeneesh
Edited by: jeneesh on Apr 13, 2009 11:36 AM
Update statements will be like as follows, if the basic design is selected :
update REPORT_MASTER set NEW_COLUMN1 = 'BRF01.1' where dynamic_condition1 and NEW_COLUMN1 is not null;
update REPORT_MASTER set NEW_COLUMN1 = 'BRF01.2' where dynamic_condition2 and NEW_COLUMN1 is not null;
update REPORT_MASTER set NEW_COLUMN2 = 'BRF02.1' where dynamic_condition25 and NEW_COLUMN2 is not null;
...Edited by: jeneesh on Apr 13, 2009 12:40 PM
Taking it to front....
Edited by: jeneesh on Apr 14, 2009 8:37 AM
Still I am not comfortable to use 37 columns..

Answer 1

APC wrote:
Not sure what you're expecting from us. I'm afraid you haven't explained your scenario clearly, so it's difficult to offer design advice. I will try to explain better:
Basically, requirement is to generate 37 (BRF01 to BRF37) reports from the table CRB_OUTPUT_VIEW_TAB.
(This is the Master Data Table - In the original thread I have mentioed it as REPORT_MASTER).
Each report needs to apply different rules. For this, a RULE table(Parameter table) is provided.
Master Data Table
SQL> desc crb_output_view_tab
Name                                      Null?    Type
COMPANY                                            VARCHAR2(240)
GLNO                                               VARCHAR2(144)
CURRENCY                                           VARCHAR2(15)
CUSTOMER_NAME                                      VARCHAR2(240)
ACC_DEAL_NO                                        VARCHAR2(29)
FCY                                                VARCHAR2(18)
LCY                                                VARCHAR2(18)
INT_EXH_RT                                         NUMBER
VALUE_DATE                                         VARCHAR2(10)
MAT_DATE                                           VARCHAR2(10)
CUSTOMER                                           VARCHAR2(50)
BRANCH                                             VARCHAR2(25)
INT_BASIS                                          VARCHAR2(10)
OGLKEY                                             VARCHAR2(207)
SECTOR                                             VARCHAR2(6)
INDUSTRY                                           VARCHAR2(6)
TARGET                                             VARCHAR2(2)
RESIDENCE                                          VARCHAR2(2)
NATIONALITY                                        VARCHAR2(2)
REPORT_DATE                                        VARCHAR2(11)
GL_DESC                                            VARCHAR2(50)
PORTFOLIO                                          VARCHAR2(10)
LOAN_TYPE                                          VARCHAR2(10)
EXH_RT                                             NUMBER
BLSHEET                                            VARCHAR2(50)
SOURCE                                             CHAR(3)
CATEGORY                                           VARCHAR2(6)
BRF_CODE                                           VARCHAR2(20)
DR_CR                                              VARCHAR2(6)
NA                                                 VARCHAR2(6)
Rules - Master Table
SQL> select * from brf_parameters order by brf_id,seq;
  PARAM_ID BRF_ID            SEQ BRF_CODE             COLUMN_NAME                    DATA_TYPE                                                                                     
         2 BRF01               1 BRF010001            GLNO                           CHAR                                                                                          
         1 BRF01               1 BRF010001            CURRENCY                       CHAR                                                                                          
         3 BRF01               2 BRF010002            GLNO                           CHAR                                                                                          
         4 BRF01               3 BRF010006            GLNO                           CHAR                                                                                          
         6 BRF01               4 BRF010008            GLNO                           CHAR                                                                                          
         5 BRF01               4 BRF010008            RESIDENCE                      CHAR 
390 BRF02               1 BRF020001            RESIDENCE                      CHAR                                                                                          
       391 BRF02               1 BRF020001            BRF_PARENT                     CHAR                                                                                          
       392 BRF02               2 BRF020002            RESIDENCE                      CHAR                                                                                          
       393 BRF02               2 BRF020002            INDUSTRY                       CHAR                                                                                          
       394 BRF02               2 BRF020002            BRF_PARENT                     CHAR    
Rules -  detail Table: (Linked to brf_parameters by param_id)
SQL> select * from brf_param_values where param_id in (1,2);
  PARAM_ID CONDITION            VALUE1                         VALUE2
         1 IN                   AED
         2 IN                   0010
SQL> ed
Wrote file afiedt.buf
  1  select p.seq,p.brf_id,p.brf_code,p.column_name,v.condition,v.value1,v.value2
  2  from brf_parameters p,brf_param_values v
  3  where p.param_id = v.param_id
  4* order by p.brf_id,p.seq,p.param_id
SQL> /
       SEQ BRF_ID     BRF_CODE             COLUMN_NAME                    CONDITION            VALUE1                         VALUE2                                               
         1 BRF01      BRF010001            CURRENCY                       IN                   AED                                                                                 
         1 BRF01      BRF010001            GLNO                           IN                   0010                                                                                
         2 BRF01      BRF010002            GLNO                           IN                   0010                                                                                
         3 BRF01      BRF010006            GLNO                           IN                   0030                                                                                
         4 BRF01      BRF010008            RESIDENCE                      IN                   AE                                                                                  
         4 BRF01      BRF010008            GLNO                           IN                   0040                                                                                
         5 BRF01      BRF010009            GLNO                           IN                   0040                                                                                
         6 BRF01      BRF010004            GLNO                           IN                   0050                                                                                
         6 BRF01      BRF010004            CATEGORY                       IN                   5001                                                                                
         6 BRF01      BRF010004            DR_CR                          IN                   Debit                                                                               
         7 BRF01      BRF010049            DR_CR                          IN                   Debit    For genarating the report BRF01 :
Updation will be done based on each "SEQ" value shown above. So..
Ist update: (Generated from SEQ = 1 for BRF_ID = BRF01)
     update crb_output_view_tab set new_brf_code_column = 'BRF010001'
     where currency in ('AED') and GLNO in ('0010');
--This is sample. it will be like : GLNO in ('0010','0040','0056'.....)IInd update: (Generated from SEQ = 2 for BRF_ID = BRF01)
     update crb_output_view_tab set new_brf_code_column = 'BRF010002'
     where GLNO in ('0010')
     and new_brf_code_column is null;..... And so on.
The data in the "new_column" is required for report generation.
After all the updations the report "BRF01" (through UTL_FILE) will be generated.
After that updation for BRF02 will be performed and report will be generated.
I have to store the data for all BRF01,BRF02.. because these are used for online reports which are accessed from Discoverer also.
What changes are you making that has lead to you considering nested tables or child tables? I have explained in detailed manner above. (Please revert if not clear)
Why would a detail table be 37 times as big as one table? I was thinking of adding a PK to "crb_output_view_tab" and a new detail table like
pk_from_crb_output_view_tab     NUMBER
brf_id                    VARCHAR2
brf_code               VARCHAR2Now here the number of rows will be 37* number_of_rows_in_crb_output_view_tab
Big in which dimension(s)? I have to join the master table and new_detail_table for each report generation
What drives the design - the updating of REPORTS_MASTER or the application which uses the updated data?The time for updation and daily generation of 37 reports (We can ignore the performance of discoverer reports)
Thanks,
Jeneesh