| Loading duplicates records into SSAS 2005 |
| Written by Thomas Ivarsson |
| Sunday, 19 October 2008 15:27 |
|
This post is about what will happen when you load duplicate dimension records into SSAS 2005. A following post will deal with duplicate fact records. Will SSAS 2005 generate an error when you try the first scenario? Not by default as we shall see in a simple cube. When you have primary keys in all dimensions, foreign keys in the fact table and a unique constraint on all the fact table foreign keys the problem with duplicate records will never occur in either the dimension tables or the fact tables. You will get errors when you load the tables in the ETL-process. In reality the data quality is not always that good or you might have performance objectives that will prevent you from having constraints in your starschema. Read more...
|
Tags: 2005, article, design
Top Rated
- SSAS Implementation Best Practices slides in PDF format
- SSRS Report Against a SSAS Parent Hierarchy
- Using AS Data Mining to Add Forecast Values to a Cube
- Handling inter-dimensional members dependency and reducing cube sparsity using reference dimensions in Analysis Services 2005
- Cube structure optimization for MDX query performance in Analysis Services 2005 SP2: Tips for Parent Child Hierarchies usage
- Handling Multiple Calendars with a M2M Scenario
- Passing MDX parameters in Reporting Services reports
- Using UserName to Control Data Access and Default Member in SSAS 2K5 (Carrie Williams)




