Awesome video! You explained my questions so well! Thank you for your sharing!
@dpclassyes1417 Жыл бұрын
One of the best best video for surrogate key... You covered all points.... Omg thanks a lot
@hayatabadcomputeracademy45163 жыл бұрын
Thanks for sharing the helpful much information in a short time.
@ramprasathselvamani86523 жыл бұрын
Very straight forward explanation. Thanks a lot.
@bbrocks55306 жыл бұрын
Please share a video on how to create a dw in step by step approach
@cajaykiran Жыл бұрын
I am newbie but still ur explanation was crystal clear. Keep up good work 👏
@SHIVAKUMAR-tk6uz2 жыл бұрын
simple and informative ..Thanks
@chiranjeevibelagur22752 жыл бұрын
Such a clarity. Thank you 😊
@reekanmohan78766 жыл бұрын
good one... keep it up
@kunalkumar-hl6gv9 ай бұрын
This is the best video on internet which talks about surrogate key
@akhilnegi1005 жыл бұрын
Great explanation
@pythonatmadhu60613 жыл бұрын
Very nice presentation
@chavelooo334 жыл бұрын
Great explanation. Thanks
@just4fun4106 жыл бұрын
Superb
@ramubuddi83965 жыл бұрын
Surrogate key plays a crucial role here, because with using surrogate key we are inserting data into a fact table in OLTP
@saurabhmani15074 жыл бұрын
we use row wid as surrogate key
@subramji6 жыл бұрын
Good one
@sridharmurari30078 ай бұрын
Straight and precise
@esraozturk44672 жыл бұрын
Perfect explanation, thanks!
@ganeshdevidashiwale53693 жыл бұрын
Great explanation..
@anugyajain87044 жыл бұрын
Thanku so much sir.... Very gud explaination
@jayashreewani62376 жыл бұрын
Great Explanation , Thx
@rishigc4 жыл бұрын
very good tutorial... keep up the good work !
@liono118 Жыл бұрын
Fantastic
@CRVgarage5 жыл бұрын
Nicely explained.
@ashirbadparida3268 Жыл бұрын
Fabulous 😍
@shwethav.r71003 жыл бұрын
Thank you so much , clearly understood...please make a video on how to create a surrogate key technics..
@mokshadakothari12653 жыл бұрын
Good information !
@user-jw5xk8id7v2 жыл бұрын
Thanq man Very informative video
@sarthaks6 жыл бұрын
Awesome!!
@sonutvv2 жыл бұрын
Best video. Thanks.
@CODwontons3 жыл бұрын
Thank you for being quick and getting to the point! Some other people's videos are too slow!!
@mayureshbehere7024 Жыл бұрын
Thank you so much sir.. Its very very Helpful to understand👌
@shwetabudake51082 жыл бұрын
Useful video
@SharoonGill12 жыл бұрын
what to do if the store_table (dimension table) is a slowly changing dimension for which we can create a surrogate key, but for sales_table (fact table) the surrogate key is not provided to identify stores (as these keys have no meaning in the real world, imagine an external data provider giving us sales data based on store IDs). How can we use this concept then?
@pulkitarun4 жыл бұрын
Your videos are awesome. There is little request if you arrange your videos in the playlist in proper order that would more helpful to your viewers. Initially all video are randomly arranged in your playlist.
@sathiyalr4 жыл бұрын
Thank you..Very helpful
@mabasha99783 жыл бұрын
Good 👍
@sarahrachel1433 жыл бұрын
superb
@SagarSingh-ie8tx Жыл бұрын
Nicely Explained ;) man
@KalyanS6 жыл бұрын
Nice Video
@suprajasreerama75616 жыл бұрын
How do we write sql script for dimension table in oracle that has a surrogate key? I am going to use informatica tool to load the dimension tables. Please let me know. TIA.
@phani98851200966 жыл бұрын
Thanks!
@karthyme6 жыл бұрын
Good video !
@SunnyKumar-wp6wp2 жыл бұрын
God level of explaination
@jagadeeshp81793 жыл бұрын
Your explanation is good, but too much speed when you speak.
@Ndegwiz2 жыл бұрын
Thanks
@AhmadAbdallah03955 жыл бұрын
thank you
@zeeshanpervaiz85702 жыл бұрын
I would just like to point out at 4:47: for SCD Type-2 if another row is added with a similar storeID, then a new surrogate_key should not be generated because S1001 SK should already be present in main SK Table. If the PK was a composite key (storeID,streetname) then a new surrogate should be generated. Rest of the stuff is very helpful. Thanks for the upload.
@wilsonman866111 ай бұрын
S1001 is not a surrogate key; it is a natural key. By definition, a new surrogate key has to be generated for every record.
@prachirandive.71953 жыл бұрын
It was amazing
@raptorslam843 жыл бұрын
another awesome video!! thank you so much.
@crazycom98073 жыл бұрын
I had a question in interview on this He asked me that the fact table has a composite PK which itself is unique and strong then why we need a SK again to uniquely identify a record...it created a lot of confusion to me and I was not able to answer it that time.
@aakashpatel27923 жыл бұрын
Surrogate keys are ideal for dimension tables but not ideal all the time for fact tables. But there are three mainly reasons when you need a SK in fact tables. 1. Sometimes business rules of organization legitimately allow to keep two identical rows into a fact table. It is not quite often but there is a possibility. As a engineer, you would definitely add some timestamp to identify those two rows as unique but occasionally you are forced to accept this undesirable input. 2. It is feasible for some ETL technique. Let's say you want to update rows in fact table and you want to design your ETL processes in a single transaction like insert updated rows as new rows in step 1 and delete old rows in step 2. This technique has significant improvements in load balancing, recovery and audit purposes. For this technique, you do require a surrogate key as there is a chance that composite key can be duplicate for new records as well old records. 3. From similar ETL perspective, it's easy to determine at which point your job suspended or crashed and you can resume from that point or run process entirely. A sequential surrogate key can help to make this task very straight forward by getting max surrogate key from fact table.
@crazycom98073 жыл бұрын
@@aakashpatel2792 thanks a lot for detailed information. It really helps👍
@nisharahman7382 жыл бұрын
@@aakashpatel2792 helpful
@adamk15205 жыл бұрын
If a previously inserted store ID changes location, you would want to have a process that ingests the file and UPDATES the already existing store ID. This model doesn't make sense because you now have two store IDs of S1001. Are they two different locations? Did one store close?
@oorishawo5 жыл бұрын
I think you are forgetting that even though there is a change in the record, of course old and new record still bear the same natural key S1001, the surrogate key of the record with updated attribute will be a different integer (SK). So, if old record is 2, the new record could be 7.
@sivakumaranbazhagan16725 жыл бұрын
So what happens to the original primary key would it still exist on dimension table and if it does, what is going to be its significance now that surrogate key is also present?
@oorishawo5 жыл бұрын
Nothing other than its used to trace - back to source data
@Buzzingfact2 жыл бұрын
where are you man...make more videos on dwh... these are great
@srikantganapati3 жыл бұрын
Speak slowly to understand better. No doubt your videos are awesome.
@grim_rreaperr5 ай бұрын
at 5:00 shouldn't it be append instead of merge?
@isadoralmeida066 жыл бұрын
Can I just say that the natual key in a dimension table from a DW correspond to the PK column to that same table from the database? And the SK column is the PK of the dimension table, so i will only exists on the DW. Is my thought correct?
@pulkitindia6 жыл бұрын
As per my understanding you are correct
@dnyaneshwarudhare10742 жыл бұрын
Pls speak slow...as like SCD...otherwise your videos are awesome
@khajamoinuddin65676 жыл бұрын
Surrogate means in SCD dimention we have to give identity column right.... surrogate = Identity column Am i right... please conform me..
@aroundBI6 жыл бұрын
Good that you asked it. With "Identity Column", if you are referring Primary Key - You are correct. Surrogate key is added as a primary key column in dimensional tables.
@tanyasinha28973 жыл бұрын
@@aroundBI Please let me know that if we add same value record in primary key column (like S1001) .it should not be possible because it has to be unique.So why do we need surrogate key in this case.
@nadeemshaikh38573 жыл бұрын
@@tanyasinha2897 I guess, surrogate key plays important role when we used scd type 2 where we keep old record and updated record as well.
@triple09ful3 жыл бұрын
so basically it is numbering 1,2,3,4 for each record. OMG what a complex concept!!
@faisalalshawkani89104 жыл бұрын
good explanations but can you please bring someone else who does not have an accent. I barely could understand you. I could not understand you at all brother.