What to look for when finding the target for table compression
Page 1 of 1
What to look for when finding the target for table compression
Hi,
I am designing a star schema for a solution and we want to use the capability of the exadata (oracle 11g)
we have standard architecture where reporting will be done at from MOLAP (fed from the star schema).
I have very little experience on the exadata capability though i understand basic feautures what I am looking for any pointer on where should i start looking at .
I mean as rule of thumb what can be put for compression or partition, any obvious big gotcha that i should avoid .
I am designing a star schema for a solution and we want to use the capability of the exadata (oracle 11g)
we have standard architecture where reporting will be done at from MOLAP (fed from the star schema).
I have very little experience on the exadata capability though i understand basic feautures what I am looking for any pointer on where should i start looking at .
I mean as rule of thumb what can be put for compression or partition, any obvious big gotcha that i should avoid .
Ashish Mishra- Posts : 11
Join date : 2011-02-22
Similar topics
» SQL Server 2008 - CHAR and table compression vs VARCHAR in Dimension Tables
» Finding association using BRIDGE table
» Sales Target Implementation in SSAS Cube
» Is is part of the current target?
» Acual Vs Target on dimension attibute
» Finding association using BRIDGE table
» Sales Target Implementation in SSAS Cube
» Is is part of the current target?
» Acual Vs Target on dimension attibute
Page 1 of 1
Permissions in this forum:
You cannot reply to topics in this forum