Results 1 for
"rapidly changing dimensions"
Rapidly changing Monster dimension...
Hi Everyone, I have a list of more than 300 attributes, which are actually part of the fact tableĀ .(basically ..these values changes for each transaction level record in fact but belongs to a single dimension). that lot contains more than a 100 date
Hi Everyone, I have a list of more than 300 attributes, which are actually part of the fact tableĀ .(basically ..these values changes for each transaction level record in fact but belongs to a single dimension). that lot contains more than a 100 date
Rapidly Changing Dimension
Hello, I have a slowly changing dimension table with 105 attributes. About 85% of the attributes are type 1 and the remaining 15% are type 2. I have 4 fields that are type 2 that change a lot more frequently than the rest of the type 2 fields. On a
Hello, I have a slowly changing dimension table with 105 attributes. About 85% of the attributes are type 1 and the remaining 15% are type 2. I have 4 fields that are type 2 that change a lot more frequently than the rest of the type 2 fields. On a
Slowly Changing Dimensions - Design Review (Need More Clarification)
Hello, Suppose I have following Fact and Dim table CustomerDim CustomerKey CustomerID CustomerNumber CustomerName CreditLimit - Slowly Changing, wants history IsAnnualMember - Slowly Changing, can be different from year to year or
Hello, Suppose I have following Fact and Dim table CustomerDim CustomerKey CustomerID CustomerNumber CustomerName CreditLimit - Slowly Changing, wants history IsAnnualMember - Slowly Changing, can be different from year to year or
Unsure about relationship with Slowly Changing dimensions.
Hi Sorry datawarehouse newbie question! I have many years experience with relational databases but my head is not yet around the dimensional model. I am not sure how to maintain the relationship between Fact and Type 2 Dimension. i.e if a new row is
Hi Sorry datawarehouse newbie question! I have many years experience with relational databases but my head is not yet around the dimensional model. I am not sure how to maintain the relationship between Fact and Type 2 Dimension. i.e if a new row is
fast changing dimension
I'm debating how to model a teacher work force where most often a teacher works for one school authority. The issue is where a teacher works for multiple school authorities. A substitute teacher for example could work for a different school authority ever
I'm debating how to model a teacher work force where most often a teacher works for one school authority. The issue is where a teacher works for multiple school authorities. A substitute teacher for example could work for a different school authority ever
How to handle Large dimensions 35M records
Hi all. I have a dimension with 35+ million records as compared to 225 Million in the fact table. I am not sure about the kind of penalty we will have to pay for such a big dimension. Here is summary regarding this dimension. This dimension is derive
Hi all. I have a dimension with 35+ million records as compared to 225 Million in the fact table. I am not sure about the kind of penalty we will have to pay for such a big dimension. Here is summary regarding this dimension. This dimension is derive
Type 3 Slowly Changing Dimension
I am trying to find a best example / scenario where a type 3 scd would make more sense than a type 2. In my understanding type 3 can easily be derived from type 2. If anybody has used type 3 dimension instead of type 2, please let me know the scenario an
I am trying to find a best example / scenario where a type 3 scd would make more sense than a type 2. In my understanding type 3 can easily be derived from type 2. If anybody has used type 3 dimension instead of type 2, please let me know the scenario an
How to load a Slowly Changing Dimension Type 2 with one SQL Merge statement in Oracle
This is based on Design Tip 107 ("Using the SQL MERGE Statement for Slowly Changing Dimension Processing") and does sth. similar in Oracle You can access the solution at http://www.business-intelligence-quotient.com/?p=66
This is based on Design Tip 107 ("Using the SQL MERGE Statement for Slowly Changing Dimension Processing") and does sth. similar in Oracle You can access the solution at http://www.business-intelligence-quotient.com/?p=66
Slowly Changing Dimension table
Hello, I have scenario where we are creating a Dimension Table and Fact Table from the same Source Table which contains both descriptive and numeric data I want to model the Dimension table as a Slowly changing Dimension Type 2 (create new
Hello, I have scenario where we are creating a Dimension Table and Fact Table from the same Source Table which contains both descriptive and numeric data I want to model the Dimension table as a Slowly changing Dimension Type 2 (create new
SCD Type 2 dimension and fact table being the same table
I am designing a dimensional model for employee data in a data warehouse. Right now I only register the basic information about the employee, like job title, department, language, FTE, etc. I have chosen to use an SCD Type 2 dimension since I want to keep
I am designing a dimensional model for employee data in a data warehouse. Right now I only register the basic information about the employee, like job title, department, language, FTE, etc. I have chosen to use an SCD Type 2 dimension since I want to keep
Monster Dimensions
My customer list is huge (about 70 millionish). We currently have a 60 million row dimension (CUSTOMER) that holds most of our existing customers, and this existing large DIM is currently performing fine for us. Now my clients want to type 2 two
My customer list is huge (about 70 millionish). We currently have a 60 million row dimension (CUSTOMER) that holds most of our existing customers, and this existing large DIM is currently performing fine for us. Now my clients want to type 2 two
Dynamic dimensions
What is the best way to handle dimensions that change depending on user parameters? For example, lets say you want "Months Since Inception" to be a dimension, because you want to bucket by it (i.e. 0 to 50 Months, 51 to 100 Months, etc.) but
What is the best way to handle dimensions that change depending on user parameters? For example, lets say you want "Months Since Inception" to be a dimension, because you want to bucket by it (i.e. 0 to 50 Months, 51 to 100 Months, etc.) but
Mini Dimensions
Hi In out data warehouse design (superannuation) we need to cater for Client and Accounts and the relationship between them (a client can have one or more accounts). Some of the client attributes can change so we were thinking or having a client
Hi In out data warehouse design (superannuation) we need to cater for Client and Accounts and the relationship between them (a client can have one or more accounts). Some of the client attributes can change so we were thinking or having a client
Advice on relationships between Type 2 SCDs ?
Hi All, I am constructing a new warehouse schema containing a number of dimensions which need to be modeled as type 2 SCDs. This is all fine and I have surrogate IDs which are being used as the FK in the facts. The challenge I have is that a number of
Hi All, I am constructing a new warehouse schema containing a number of dimensions which need to be modeled as type 2 SCDs. This is all fine and I have surrogate IDs which are being used as the FK in the facts. The challenge I have is that a number of
Sparse dimensions, how to handle?
I've purchased the book "The Microsoft Data Warehouse Toolkit" and have reviewed it in order to build out a data warehouse solution I am currently designing. I am stuck in a spot that I don't seem to find any examples of , or am not abl
I've purchased the book "The Microsoft Data Warehouse Toolkit" and have reviewed it in order to build out a data warehouse solution I am currently designing. I am stuck in a spot that I don't seem to find any examples of , or am not abl
Results 1 to 15 on 220
for "rapidly changing dimensions"
for "rapidly changing dimensions"
Active topics
Popular topics
Unanswered topics
