COGNOiSe.com - The IBM Cognos Community

IBM Cognos 8 Platform => COGNOS 8 => COGNOS Connection => Topic started by: abhijeet364 on 02 Mar 2012 11:06:45 AM

Title: Table Partioning
Post by: abhijeet364 on 02 Mar 2012 11:06:45 AM
Hi ,

Guru's need a help. We are using Oracle as our DB. Current our ETL team is performing table partioning on the fact table's to do performance improvement. So just wanted to know whether this would affect the report's which are using this table.

Regards,
Abhijeet
Title: Re: Table Partioning
Post by: abhijeet364 on 10 Apr 2012 02:36:45 AM
Hi Techies,

Looking for your help. Its very urgent..

Regards
Abhijeet
Title: Re: Table Partioning
Post by: MFGF on 10 Apr 2012 03:35:15 AM
Why not create a dummy table, build a report on it, partition the table and see if your report still works - this would answer your question. If it's as urgent as you imply, it would seem to be a quick, easy way to resolve the urgency.
Title: Re: Table Partioning
Post by: blom0344 on 10 Apr 2012 02:50:46 PM
Partitioning is no magic wand. If - for example - you partition on year and most reports will use temporal selectivity than performance may improve dramatically since only part of the data will have to accessed.  However , other type of selectivity may negate the partitioning since all data will need to be scanned..

The proof is in the pudding   ;D
Title: Re: Table Partioning
Post by: wyconian on 03 Aug 2012 08:58:39 AM
Hi

I think the changes made in the database need to be reflected in the FM model as well.  For example  if your DB guys have added a partiton key (a column used to identify which partition a record should be placed in) you may  need to add that into part of the relationships into the fact.