Ch.02-26 Dimension Types: Multi Valued Dimension | Data Modeling | DWH Architecture

[@mesharibuhadi1437]

Thank you so much. Good work Mashallah

[@GarageEducation]

Thanks for your comment! Happy you like it

[@shrouqmedhat7116]

احنا ليه عملنا bridge ب AuthorGroup ليه معتمدناش علي AuthorGroupRelation علي طول؟ شايفة انه كان هيحل المشكلة لوحده من غير ما نعمل ال AuthorGroup

[@nidafatima7268]

Please provide English subtitles.

[@GarageEducation]

We are currently preparing another version in English. But we will check this option ASAP. Thanks

[@ahmedsalama6033]

in the final implementation is the ID of AuthorGroupRelation , ID will be repeated for authors who are in the same article ?? and in the AuthorGroup the ID will be the Distinct value for these repeated IDs in the AuthorGroupRelation ???? it will be splendid if you have a drawing board and use it to clarify more

[@Ahmadistallking]

انا عندي مشكلة مع الslides, هى clustered جدا فيها كلام كتير, الأمثلة مش ابسط حاجة بعد تلت ساعة باتوه. دا مش اول كورس Data engineering ليا ومش اول كورس database, بس فعلا انا باتوه في وسط دا

[@OmarAbdelaziz__47]

عندي سؤال بخصوص الـ Bridge Table و حاولت ادور ومش لاقي. هل وجوده بيأثر علي الGranularity ولا لا? A

[@GarageEducation]

Yes, if you haven't handle the granularity level correctly this dimension will not work well with you.

[@mosheraahmad7342]

Can we add Weighting_factor itself in the fact table and change the total order calculation to be unit_price* Weighting_factor? This way we will provide Weighting_factor and bring each author sales that may be important by business point of view

[@GarageEducation]

Hi Moshera, As per my understanding, you need to move the Weighting_factor from AuthorGroupRelation to ArticleSales and calculate the order to be unit_price * Weighting_factor. I think this solution will not work as Weighting_factor will be connected to the AuthorGroupRelation not the author himself. I tried in this video to provide the scenario before and after to make it clear. please inform me which part you need to change and I will try to think about this with you.

[@mosheraahmad7342]

Another comment, the relation between Sales and Articles is one-to-many, governed by the quantity field, so one sale may contain many articles, you mentioned that the relation between fact and dim should be one-to one, please clarify

[@GarageEducation]

Every row in the Sales contains only one article only and if we have multi article in the same order it will be added in the quantity not as a new row so, it will be one article per sales order row. I hope this is clarify the confusion for this example.

[@ibrahim47]

Why can't I simply do something like this: drive.google.com/file/d/1ZbuxFfUL58a1k5wUBaU1XZ3uAEkRuJbZ/view?usp=sharing this is usually what I would do in a normal operational DB, does the fact that this a DWH change anything?

[@GarageEducation]

It is very nice idea, I would like to discuss it with you. Could you please message us in our fb/twitter accounts?

[@ibrahim47]

@@GarageEducation My honor والله 😍

[@ibrahim47]

I sent a msg on facebook

[@GarageEducation]

@@ibrahim47 I will reply to you asap.