Skip to main content

When is snowflaking of dimensions required

There are few key factors need to be considered to decide on snowflake schema  as a data model in DW initiative
  • Frequency of dimension attribute change
  • No of dimension attributes - Large dimensions
  • Hierarchies within the dimension attributes
  • History tracking of dimension attributes

Consider type 2 SCD implementation is used for history tracking.
If a dimensional table has 10 dimension attributes and only one among the dimension attributes is frequently changing in many rows,
then table becomes huge causing performance issues and unnecesary space consumption by rarely changed dimension attributes.
Move the frequently changed dimension attribute to a seperate table and maintain RI with main dimension table,
Thus snowflaking the dimension to avoid performance issues and unneccesary space consumption

If there are hierarchies within the dimension attributes,then keying between Aggregate facts and dimension table(with hierarchies) is not appropriate
A record in sales fact will contain a store key,granularity of the fact table is product by store by day.
This means the lowest level in geography dimension is store.The hierarchy in the dimension is store, district, region
If we have all hierarchies of geography dimension stored in one table then there is no single key for district or region as the dimension table has only unique key for store
By normalizing the dimensional hierarchies,we can provide single dimension keys(district key ,region key) to aggregate facts

Final note is to remember  evaluating tradeoffs between ease of use and ease of maintenance with snowflake schema as
normalizing dimensions will involve more joins may result in degrade in query performance

Advantage of snowflake schema
The main advantage of the snowflake schema is the improvement in query performance due to minimized disk storage requirements and joining smaller lookup tables. The main disadvantage of the snowflake schema is the additional maintenance efforts needed due to the increase number of lookup tables.


Labels:

Comments

Post a Comment

Popular posts from this blog

Informatica Powercenter Partitioning

Informatica PowerCenter Partitioning Option increases the performance of PowerCenter through parallel data processing. This option provides a thread-based architecture and automatic data partitioning that optimizes parallel processing on multiprocessor and grid-based hardware environments. Introduction: With the Partitioning Option, you can execute optimal parallel sessions by dividing data processing into subsets that are run in parallel and spread among available CPUs in a multiprocessor system. When different processors share the computational load,large data volumes can be processed faster. When sourcing and targeting relational databases, the Partitioning Option enables PowerCenter to automatically align its partitions with database table partitions to improve performance. Unlike approaches that require manual data partitioning, data integrity is automatically guaranteed because the parallel engine of PowerCenter dynamically realigns data partitions for set-oriented trans
6 comments
Read more

Data virtualization

Data virtualization is a process of offering a data access interface that hides the technical aspects of stored data, such as location, storage structure, API, access language, and storage technology. Analogous to concept of views in databases Data virtualization tools come with capabilities of  data integration, data federation, and data modeling Requires more memory caching Can integrate several data marts or data warehouses through a  single data virtualization layer This concept and software is a subset of data integration and is commonly used within business intelligence, service-oriented architecture data services, cloud computing, enterprise search, and master data management. Composite, Denodo, and Informatica are the largest players in the area of data virtualization References for definition: http://www.b-eye-network.com/view/14815
7 comments
Read more

Difference between server jobs and parallel jobs in Datastage

Server job stages do not have in built partitioning and parallelism mechanism for extracting and loading data between different stages. To enhance the speed and performance in server jobs is to     - Enable inter process row buffering through the administrator. This helps stages  to exchange data as soon as it is available in the link.     - Using IPC stage also helps one passive stage read data from another as soon as data is available. In other words, stages do not have to wait for the entire set of records to be read first and then transferred to the next stage.    - Link partitioner and link collector stages can be used to achieve a certain degree of partitioning paralellism. All of the above features which have to be explored in server jobs are built in datastage Parallel jobs . The Px engine runs on a multiprocessor sytem and takes full advantage of the processing nodes defined in the configuration file. Both SMP and MMP architecture is supported by datastage Px. Px ta
1 comment
Read more