Building Making It Happen
Building Making It Happen
  Sign-in         Register
    
Principles and Rules Listing Page
Aggregation Queries on slowly changing Dimensions
There are various ways to have the aggregate queries on dimensional tables. However, one needs to have some other tricks for slowly changing dimensions.
 
This page of 'Principles and Rules' is linked to:  Data Warehousing, Data Analysis/OLAP, BI platform Tools Evaluation,


Refer to Slowly Changing Dimensions and Dimensional Model schema for a context.

There are many aggregate queries done on dimensional tables, like number of customers using a given product, or number of offices selling through third party channels, or number of sales agents who have joined in last 12 months.

This is easy if the dimensional attribute over which the query is done is not a slowly changing dimension. For example, the count of customers who were belonging to a given location/state, or count of "inactive" customers in a given month, quarter, date.

One way is:

Build Status_begin_date and status_end_date for a given attribute change in the dimensional table. For example you can have the begin-date and end-date for a customer status (active or inactive). If you run a query on the number of customers who were active on May 31, 2006, the query will filter out all the records where the "customer status" is "Active" and where the begin_date <= May 31, 2006 and end_date is >= May 31. With the above logic, you have to make sure that every time an attribute changes, a new record is created for the gives dimension..The begin date has to be one day+ status_end_date of the previous record. This is essentially the slowly changing dimension (method 2).

   Access more details on this page   

Quick Feedback- Was this information helpful ?
Relevant Links to this page
Principles & Rules → Add extra buffer for ETL phase → Principles & Rules → Homework before interviews is must (Business Requirements Phase in Data Warehouse) → Principles & Rules → Excel is the competition, which should be challenged → Principles & Rules → Avoid Pure MOLAP → Practice Techniques → Field Tips Series- Streamlining & Cost-Reduction in Business Intelligence- Consolidate Data-Marts → Practice Techniques → Field Tips Series- Streamlining & Cost-Reduction in Business Intelligence- Licensing & Maintenance Contracts → Practice Techniques → Field Tips Series- Streamlining & Cost-Reduction in Business Intelligence- Governance & Standards → Practice Techniques → Field Tips Series- Streamlining & reducing cost of Business Intelligence- Evaluate Open Source → Principles & Rules → Master Data Management- Making a Right Start → Practice Techniques → How to integrate stand-alone BI environments- Gradual Approach → Principles & Rules → Business owned applications are a reality- Manage it → Principles & Rules → New Data Standards- What about existing data and applications? → Principles & Rules → Handle Each Time-stamp in the Fact Table as a separate dimension → Principles & Rules → Keep Aggregates and Details data in different Fact tables → Principles & Rules → Some considerations for Infrastructure in Data Warehouse → Principles & Rules → For Core BI platform go for a single, established and robust player → Principles & Rules → Don't be guided only by the business requirements for your Business Intelligence → Practice Techniques → Using Synonyms and Views → 
 
Back
Featured Pages
Checksum for changed records
Data Quality Assurance Checklist
OLAP Architecture choice
Customer Data Correction and Techniques

Make 'Executable' Strategy
Maximize Results
Maximize People
Manage Execution

Featured Pages
Master Data Management vs. BI vs. Metadata
BI Competency Centre- Strategize Phase
Customer Data Correction and Techniques
Multiple Path Hierarchy