Ralph Kimball and other Kimball Group members have written over 120 columns for Intelligent Enterprise Magazine and its predecessor, DBMS Magazine.
How do you cope with an executive's request to "bring back a time series of activity for all subscribers who were in platinum status as of X date," or "show me a time series of orders by sales region according to the sales organization as of Y"? Here's how data warehouse pros can cope with the common requirement to look back in time.
These 34 subsystems cover the crucial extract, transform and load architecture components required in almost every dimensional data warehouse environment. Understanding the breadth of requirements is the first step to putting an effective architecture in place.
Design Tips 2006 (PDF format)
|
| Design Tip #86 |
|
Reference Dimensions for Infrequently-Accessed Degenerates
|
| Design Tip #85 |
|
Smart Date Keys to Partition Fact Tables |
| Design Tip #84 |
|
Readers’ Suggestions on Fact Table Surrogate Keys
|
| Design Tip #83 |
|
Resist Abstract Generic Dimensions |
| Design Tip #82 |
|
Pivoting the Fact Table with a Fact Dimension |
| Design Tip #81 |
|
Fact Table Surrogate Keys |
| Design Tip #80 |
|
Dimension Row Change Reason Attributes |
| Design Tip #79 |
|
Dangerously Large Dimension Tables
|
| Design Tip #78 |
|
Late Arriving Dimension Rows |
| Design Tip #77 |
|
Warning: Summary Data may be Hazardous |
| Design Tip #76 |
|
Advantages of a 64-bit Server
|
| Design Tip #75 |
|
Creating the Metadata Strategy
|
Design Tips 2005 (PDF format)
|
| Design Tip #74 |
|
Compliance-Enabled Data Warehouses
|
| Design Tip #73 |
|
Relating to Agile Methodologies |
| Design Tip #72 |
|
Business Process Decoder Ring |
| Design Tip #71 |
|
Naming Conventions |
| Design Tip #70 |
|
Architecting Data for MS SQL Server 2005 |
| Design Tip #69 |
|
Identifying Business Processes |
| Design Tip #68 |
|
Simple Drill-Across in SQL |
| Design Tip #67 |
|
Maintaining Back Pointers to Operational Sources |
| Design Tip #66 |
|
Implementation Analysis Paralysis |
| Design Tip #65 |
|
Document the ETL System |
| Design Tip #64 |
|
Avoid Isolating the DW and BI Teams |
| Design Tip #63 |
|
Building a Change Data Capture System
|