Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Search results for query: *

  1. bootsminimus

    Duplicate dimensions for different facts?

    Hi Greg, I'm coming in very late into this thread but you might like to look at the design tip #87 on the Kimball Group web site. See http://www.rkimball.com/html/07dt/KU87CombiningSCDTechniques.pdf. It explains here how it might be possible to combine SCD1 and SCD2 on the same dimension and...
  2. bootsminimus

    Putting dimension attributes in fact tables

    Hi Greg, I may have misunderstood the requirements and I'm not certain of the contents of your 'transaction' fact table. From your last entry it does seem that you need to be able to view the dates that the status of the 'equipment' dimension changes and the 'transaction' fact doesn't (easily)...
  3. bootsminimus

    Halfway between type 1 and type 2

    I must say I never saw the bridge table (store-chain) as having to be updated as I would expect the ETL process to add the latest keys to the bridge. However the introduction of another join to get chain information would degrade performance compared to the 1st prize of having the chain data...
  4. bootsminimus

    Putting dimension attributes in fact tables

    This discussion took on a life of its own! I would like to try my hand at answering the original question about the changing statuses in a dimension that need to be recorded. It seems that Greg is reluctant to use the status on the "equipment" dimension as a type 2 change. I think this would...
  5. bootsminimus

    Halfway between type 1 and type 2

    Thanks johnherman for your input. I must say that we have had to resolve an number of problems using a bridge type solution and I can see that it would work in this situation as well. You are right about the advantage it gives in providing a proposed store/chain change that's expected in the...
  6. bootsminimus

    Halfway between type 1 and type 2

    Thanks Hans63 for your response. We could try to address this by making all changes SCD type 2 but then any modifications to the chain code and chain name would cause a type 2 change and give the incorrect result. They need to behave as a SCD type 1 change but only affecting rows where the chain...
  7. bootsminimus

    Halfway between type 1 and type 2

    I think everyone has got the gist of the problem. I am interested to note that it appears to be an unusual problem. Has nobody had to solve this problem before? For now the store dimension holds predominately type 1 attributes and the chain number is the only type 2 attribute and there is a...
  8. bootsminimus

    Halfway between type 1 and type 2

    Consider the following: A store dimension has a type 2 attribute of chain. A chain is higher in the store's hierarchy and has a number of related attributes that have been denormalised and held on the store dimension. It is possible that the store can move chains and for reporting purposes the...

Part and Inventory Search

Back
Top