Great video man...... u deserve some applause......I' m having my database exam on 11 th nd i was having confusions in retaional data model. But, I learnt from this vedio, now i fell i can do well in my exam😇
there is a small remark: relation manages has an attribute so it should be converted into a table having 2 tables PK in addition to attribute start date
Shouldn't DepartmentID be part of the Locations table? This instead of LocationID being part of the Department table. Department-Location becomes a 1:M relationship once you convert Locations into a new table, which causes the PKey of side 1 to become a FKey in side M.
Hey and thx for watching and commenting! I have reviewed the video and the theory behind and your are correct. DepartmentID should indeed be part of the Locations table. Otherwise it will be a 1:N relationship. I will note it in the video and the comments. Thank you for noting this mate.
was very helpful, u managed to explain 1:n, m:n, derived attributes, multi valued attributes and many other things with a single example, it was great. subscribed :D
Great video! But just a quick question. shouldnt't startDate be an attribute of Employee and not Department, as it is related to an employee... or does it mean the startDate of the department
Why for the relation "works on" we created a seperate table, but for the others relations ("work for" .. and so on) we added attributes to the already existed entity sets instead?
Great Explanation. I have one think to say. I think you missed a Derived Attribute called NumbersOfEmployees. Is there any intention for that? If you really missed it, give me a idea how to do that. Thank you.
Hello, I have a question. Revising the Department - Location relationship, I think the Location should store the DepartmentID as multiple locations are available for one single department. So, if I see things correctly, a LocationID in the Department table cannot handle multiple locations.
Hey and thx for watching and commenting! We can calculate / query the derived attribute value based on the other attributes in the DB, therefore a derived attributed should not be created in the DB.
why manage relation didn't create new table because it has an attribute called startdate, because you create it for workson relational with hours attribute.
The multivalued location table should have had dept I'd instead of the dept table having location id? Also the start date should have belonged to employee table and not the dept table. Can anyone help me out here?
Q1: CONVERT Following Entity Relational Diagram into Ralations and also write SQL commands for designing these relation into Oracal Database. This question solve from the given table in video
If you refer to ProjectID then no, since Department-Project has a 1:N relationsship and therefore we must put a Foreign Key from the 1-side (departmentID) to the N-side (Project table). Hope it makes sense.
Was able to make a relational data model without any prior experience. This model will be used for many great things.
2hr of lecture in 11min 🔥♥️
Hey and thx for watching and commenting!
Great video man...... u deserve some applause......I' m having my database exam on 11 th nd i was having confusions in retaional data model. But, I learnt from this vedio, now i fell i can do well in my exam😇
How did it go? I got my exam coming soon too lol
Great Man. Such TH-camrs are really needed now a days 🤝🏻🥺❤️
this is good lecture can help many people who need to understand about ERD
Best video ever....don't stop uploading man
God bless you I was searching for two days for this !! thank you very Much, Bro
Thank u so much!! You Cleared the concepts in a single example 😄
I am sorry that I have to say, that I as a German, had to laugh about your name but after that you saved my ass with that video.
there is a small remark: relation manages has an attribute so it should be converted into a table having 2 tables PK in addition to attribute start date
Shouldn't DepartmentID be part of the Locations table? This instead of LocationID being part of the Department table. Department-Location becomes a 1:M relationship once you convert Locations into a new table, which causes the PKey of side 1 to become a FKey in side M.
Hey and thx for watching and commenting! I have reviewed the video and the theory behind and your are correct. DepartmentID should indeed be part of the Locations table. Otherwise it will be a 1:N relationship. I will note it in the video and the comments. Thank you for noting this mate.
Thanks!
Brilliant video. A gem of a video for this topic, possibility the best on youtube :)
Hey and thx for watching and commenting!
was very helpful, u managed to explain 1:n, m:n, derived attributes, multi valued attributes and many other things with a single example, it was great. subscribed :D
Great video. Concise and straight to the point. Thanks a lot.
Life saver!!!!
Extremely simplified and well explained ❤❤❤❤❤
Hey and thx for watching and commenting!
Thank you. The ER diagram website is useful for my database homework.
Great video! But just a quick question. shouldnt't startDate be an attribute of Employee and not Department, as it is related to an employee... or does it mean the startDate of the department
THIS was quite helpful. Thank you!
Hey and thx for watching and commenting!
thx brother for this best exp. ı know all northern people if they want is the best programmer in the world
Very helpful video... Helped me a lot in my exam
Hey and thx for watching and commenting!
Why for the relation "works on" we created a seperate table, but for the others relations ("work for" .. and so on) we added attributes to the already existed entity sets instead?
this is probably very late but we did that because its a many to many relation
Great Explanation.
I have one think to say. I think you missed a Derived Attribute called NumbersOfEmployees. Is there any intention for that? If you really missed it, give me a idea how to do that.
Thank you.
Please could you share the guide that you showed in the video to translate ER diagram to the Relational Data Model.
Finally non indian youtuber 😁
does not matter
@@ziyadAlshareef04matter
,😅 we don't have 500+ genders in our country 😂, and just to add 😂 u r non Indian youtubers are busy in prawn 🍤 sites
indians are awesome
Raci$t
Hello, I have a question. Revising the Department - Location relationship, I think the Location should store the DepartmentID as multiple locations are available for one single department. So, if I see things correctly, a LocationID in the Department table cannot handle multiple locations.
Yes, actually we shud have either one more extra table for deptis locid , dptid will be fk so it can be repeated
Super and very easy to understand ! Just like a school teacher.
Hi, thanks for the video. BTW, link to conversion guide is not working.
yup same here
Hey this video is really helpful!! Can you post more on creating ER diagram from a given situation/problem statement?
Thankyou for the lecture sir it cleared my doubt
Why was the derived attribute ignored?
Also, can the StartDate attribute rather be in the Employee table?
thanks!
Hey and thx for watching and commenting! We can calculate / query the derived attribute value based on the other attributes in the DB, therefore a derived attributed should not be created in the DB.
Aren’t we supposed to take the primary key on the many side and store it in the 1 side?… I’m just asking cuz that’s what our lecturer taught us
Thank you for this video! Extremely helpful.
Du bist toll!
why manage relation didn't create new table because it has an attribute called startdate, because you create it for workson relational with hours attribute.
My English isn't good. His accent is just fine for me. Good work dude!
Hey and thx for watching and commenting!
Great video
I have to do this whole presentation for class and also do the data input in sql
Great video cleared all doubts and very good explanation
Great explanation. Simple to understand. Thank you so much...
Hey and thx for watching and commenting!
Love uuuuuu 💋💋💋💋 a savior fr
Thank you very much. It helps with my assignment.
Very helpful, cleared a lot of doubts : )
Hey and thx for watching and commenting!
What im not anderstand the Location in Two Babbel. Why do you dont use the racktingle and reagionships?
Thank you for the tutorial, can you provide a new link for the ER conversion guide.? Since the one in description doesn't work. Thanks
Thank you very much bro♥️ You are a life saver!!
Hey and thx for watching and commenting!
are there any examples with more complex models? with double line relations?
what to do when the relationship is 1:1?
For one to one relationship we have to create a different table?
Is it unnecessary to create the tables "WorksFor", "Manages", and "Controls"?
Or did you just leave it undone?
Extremely useful, thank you for sharing sir.
Thanks for the video, but the conversion guide is inaccessible
The multivalued location table should have had dept I'd instead of the dept table having location id?
Also the start date should have belonged to employee table and not the dept table.
Can anyone help me out here?
Very helpful. Thanks alot, but I think that the relationship of Employee manages Department is one to one relationship not one to many. THANKS
IRL one person can manage multiple departments.
I think it didn't include the constraint, participation(full/partial) ...
Hey and thx for watching and commenting!
It still looks like DepartmentID can only have 1 LocationID. How would you have multiple locations?
Unfortunately the link to conversion guide aint working for me 😥. Great video btw thanks 🔥🔥🔥
Very helpful. Thanks alot
Hey and thx for watching and commenting!
Sir, department table should have projectID as foreign key
Thanks for the video but you made table for works on but didn't make one for manage why?
Very nice very awesome pls go ahead with a new lessons 😂❤️❤️❤️
Someone please tell me why the startdate attribute is in the department table?
Very interesting video except for the normalization 1NF, 2NF ... XNF especially for the table department.
What happens to the derived attribute? :)
Q: Shouldn't the derived attribute be added at the Department table? If No what's the point of having it?
the link isn't working I have an exam soon can you please update the link asap? Thankyou!
Q1: CONVERT Following Entity Relational Diagram into Ralations and also write SQL commands for designing these relation into Oracal Database. This question solve from the given table in video
Hey and thx for watching and commenting!
hey! thanks for this video :)) I can't get access to the link of the guide tho...
so touching for an excellent video
does it matter which way the arrows point when connecting the tables at the end?
Yes,ofcourse
Thank you, Easy to understand
Hey and thx for watching and commenting!
is that relational model or crow foot model?
I have a doubt , the locationId in the location table applied from where?
Thank you for the tutorial. But I had question about the NumberOfEmployees attribute. Did you ignore it or it doesn't belong anywhere?
The link no longer works. Can you please provide an updated link?? Thanks!
for the multivalued location is it better to put the PK of the department on the location table as a foreign key?
Thank you sir for very clearly explaination
hi, what happened to the relations 'manages' and 'works_for'?
Thank you so much bro, video is super helpful
why to put startdate inside department
You didn't taught how to map that "NumberOfEmployees" derived attribute to Relational data model!!
Derived attributes will not be added as columns to the table. That's the rule. It is 'derived' right? Derived from other attributes
very helpful video! However, they taught me an attribute on a 1 to many relation isn't allowed (startDate on the relation 'manages') is this correct?
idk if you will reply or no but what is this app name??
sir the link to conversion guide is not working
Thank you, sir ...all concepts are clear
Hey Suman, and thank you for stopping by the video!
Does anyone know the software he is using to create ER diagram? Plz tell me
So how to convert relational model into the normal er diagram?
The linked website has already been removed. Could you please share the new link?
thank you sooo much for this explanation
Does anyone have the conversion guide pdf? the link no longer working.
Hi, the converting document link is not working :(
Hey How to use rules for aggregation ,where is PK, FK? Thanks in advance
what about manages relation?
this tutorial is awesome ✌✌✌
hallo! thanks for the video! do you still have the guide? the link is not working anymore! thanks a lot!!
Can I still get the document form the conversion guide?
Nice Content, Keep it up.
Hey and thx for watching and commenting!
what's the difference between primary key and foregin key?
Conversion Guide PDF - NOT FOUND
spangsberg.net/dl/FromERToRelationalModel.pdf
thanks
please can you answer me 😔
can we move ProductId to department table ? we can have relationship right??
If you refer to ProjectID then no, since Department-Project has a 1:N relationsship and therefore we must put a Foreign Key from the 1-side (departmentID) to the N-side (Project table). Hope it makes sense.
@@srenspangsbergjrgensen2419 thnx
And what about 1 to 1 relation?
Quick question. Why is NumberOfEmployees not represented in the relational model?