Database Design Tutorial utilizing Visio and Microsoft SQL Server Express 2014. This is an introduction to database design through the first three normal forms.
Пікірлер: 127
@Ckrispbacon4 жыл бұрын
I have been struggling for two weeks trying to understand many-to-many and this example made it all clear now. You're the best!
@angelamalik94376 жыл бұрын
I cannot fault anything about this video. It's simple, and you've presented the information in an elegant, clear manner at a steady but not-too-slow pace, and the information is so incredibly useful. That bridge table idea is exactly what I was needing to solve my DB design. Thank you for sharing your knowledge!
@keithrusso86815 жыл бұрын
Thank you for taking the time to create this tutorial. Sharing your apparent years of accrued knowledge has saved myself and others countless hours of frustration. Because of your tutorial, I'm not even thinking about smashing the wife's favorite coffee mug anymore. Thank you again, sir.
@mrbranmar3 жыл бұрын
@Lh Lh no he's 12 and a half
@_rahiali5 жыл бұрын
no one has ever made this any simpler than this video. thanks very detailed, great examples, and thank you
@sparshkhurana5390 Жыл бұрын
This is actually perfect, I had a good understanding of this but this has cleared all my doubts and solidified my knowledge.
@Eag7576 ай бұрын
Thank you for presenting such explanation that isn't provided on my online studies.
@terrysennette59384 жыл бұрын
Excellent work! Thank you so much for this training!!!
@luckytechpro95373 жыл бұрын
U reminded me one of my funny Lecturer whos teaching me this Unit{Database}...Above all, u r amazing. Thanks, Sir.Greetings from Kenya
@Solrac777773 жыл бұрын
I appreciate the great explanation, thank you! Saved me allot of time :)
@cgme70764 жыл бұрын
Extremely concise. Thank you!
@akarshjaiswal16223 жыл бұрын
Amazing... Love from India !
@amitjoshi57985 жыл бұрын
Best tutorials one can have. Thanks a ton!
@purpleplasmaindustries44604 жыл бұрын
Fantastic video. Thank you for creating this!!
@davidyergensen45096 жыл бұрын
This was a very helpful and informative video. Thank you. I'm looking forward learning more.
@runthomas6 жыл бұрын
thank heavens i came across you......i am designing a datbase for django ...and i was completely wrong in my approach and duplicating and throwing htings around all over the place...now im gonna start again and try and get a better design.
@thearchibaldtuttle6 жыл бұрын
Important to know: Reverse engineering for databases exists only up too Visio 2010. That was an extremely good feature to create nice looking ERD for documentation purposes.
@cphoenix07 жыл бұрын
excellent, thank you for making this video, very helpful!
@ramseybeing4 жыл бұрын
Thanks this gave me some clarity!
@kennethmcquade43415 жыл бұрын
this is brilliant, thank you
@truckstomotorcycleswithtom31973 жыл бұрын
Just learning SQL and this helps on the many-many relationship
@DataRevolution103 жыл бұрын
Awesome way of explaining...Thanks!
@Brad106 жыл бұрын
Thank you for the upload! Do you know if Dr. Gogolin has a series of videos or a channel anywhere? I was able to grasp the concepts he was talking about a lot better than most instructors.
@jonghunpark14035 жыл бұрын
This is just awsome! Thanks so much.
@BackToBackSWE4 жыл бұрын
thanks for this!
@suriyav91573 жыл бұрын
Thank you for explaining based on practical corporate experience
@prasathj74364 жыл бұрын
Fantastic tutorial Sir. Thanks a lot.
@lampshade54375 жыл бұрын
Super helpful, thanks!
@chrisscottdoes3 жыл бұрын
Excellent video! Thank you
@luisegonzalez38055 жыл бұрын
A very nice explanation, thank you for the tutorial.
@gloryjeansqueaky7 жыл бұрын
This was incredibly helpful! I am designing my first database for my mother's daycare business. I liked the idea of separating the Orders from the Products, but I don't know if I that's how I should create the classes in my database. I have a table with classID and location and capacity. Then I have a Student Table and a Teacher Table. Right now I have tacked on to each the Student and Teacher tables a field called ClassID where you can plug in the ClassID to which they belong at the moment. But then I was thinking after watching this video, if it's better design to have a separate table which has ClassID and PersonID only. That personID can either be a TeacherID or a StudentID so that the table would reflect every person tied to that particular class. I'm double thinking my design.
@GoSparker7 жыл бұрын
MGELC - one of the most common responses to database design questions is "it depends." In your case if you have the ClassID in the Student and Teacher tables then you can only have one instance of a class for each student and teacher. In other words, you won't see history. For example, I can put the ClassID into the Student table and see what class the student is currently in, but if you move the student to another class then the ClassID changes in the Student table and you don't have a record of the previous student class relationship. If you have a bridge table between Student and Class (let's call it StudentClass) and have the StudentID and ClassID in the StudentClass table as well as a start and end date you will be able to keep track of all of the classes a student has been in. Similar with the Teacher and Class relationship. The other thing that the StudentClass table can do for you is allow a student to be in more than one class at a time.Another part of the "it depends" question is how important is it to know if a student was in another class? If you don't care then you may not have a use for the StudentClass table and perhaps could just use a comment field in one or more of the tables to handle some details. The problem with comment fields is that they can be hard to use in queries - particularly in joins. Hope this helps.
@kbdavis00077 жыл бұрын
MGELC a link table is what you are looking for 😀 a table that just provide links to related data
@lasujacob6 жыл бұрын
you can connect with me on whatsapp +256787867812
@ambars57474 жыл бұрын
@@GoSparker That's a great answer and very helpful. Thanks!
@chandra33703 жыл бұрын
Thanks for this awesome lecture
@shashankkr10087 ай бұрын
Very good explanation, thank you!
@joshuafancher31116 жыл бұрын
Thanks for the tutorial!
@njoroge20614 жыл бұрын
Am a newbie in Ms access i think the data design is quite helpful
@mochasteak4 жыл бұрын
Great explainer, thanks.
@peterlyon1852 жыл бұрын
Thank you so much for this video 🙏🏼
@true_human_0076 жыл бұрын
thanking you Very helpful video
@watummoses69114 жыл бұрын
thank for this wonderful tutorial
@karolidomisiani2826 жыл бұрын
Thanks for your good work
@ashwinimudaliar98012 жыл бұрын
so nicely explained..thanks!
@biruksisay37177 жыл бұрын
Thank you !
@namalvlogs37907 жыл бұрын
biruk sisay
@kazititu6 жыл бұрын
Sir , Thank you for the lecture, it cleared up lot of things that i didnt understand before? do you have any other videoes on relational databse design and implementation?
@MrKatdar4 жыл бұрын
great explanation, thanks
@brandonmohammed22343 жыл бұрын
HELL IS REAL HEAVEN IS REAL GOD IS REAL JESUS IS THE SON OF GOD ALL THOSE WHO ARE NOT SAVED WILL GO TO HELL AND HELL IS TORTURE FOR ETERNITY BURNING IN NEVER ENDING FIRE, ONCE YOU ARE IN HELL THERE IS NO WAY OUT, HOWEVER RIGHT NOW IT IS POSSIBLE TO PREVENT YOURSELF FROM GOING TO HELL AND BECOMING SAVED AND THERE IS ONLY ONE WAY OUT AND THIS WAY IS JESUS, JESUS DIED AND ROSE AGAIN AS A SACRIFICE FOR OUR SINS SO THAT WE DON'T HAVE TO GO TO HELL AND WE CAN HAVE EVERLASTING LIFE SO WE CAN SPEND ETERNITY WITH HIM IN HEAVEN WHICH IS PURE PARADISE. ALL YOU HAVE TO DO IS TO PUT YOUR FAITH IN JESUS AND TRUST THAT HE WILL SAVE YOU AND THE HOLY SPIRIT WILL MAKE HIS HOME IN YOUR HEART AND LEAD YOU ON THE RIGHT PATH. DON'T DELAY IN TRUSTING JESUS BECAUSE WE CANNOT TELL WHEN IT IS TOO LATE. JESUS IS COMING SOON PLEASE BE READY AND MAKE THE RIGHT CHOICE
@ArthurFreitag6 жыл бұрын
really well explained
@souryamajumdar32256 жыл бұрын
Very good tutorial
@BRP-Moto-Tips Жыл бұрын
Thanks mate 👑
@dadasajad87415 жыл бұрын
thank you sir.
@victoriagabaldon84692 жыл бұрын
Thank you Super Helpful!
@moz84057 жыл бұрын
Lovely. :)
@flexi33032 жыл бұрын
First letter of each word is capital in ZipCode is Pascal Naming convention, Camel case naming convention is zipCode first letter will be small of the word, after that first letter will be capital
@umakiruba66536 жыл бұрын
Great example...
@Fractal80Y6 жыл бұрын
Is it correct that OrderProducts and Products should NOT be plural?
@shwetha22895 жыл бұрын
Why we can't we use both orderID and product ID as composite key in this?why we use line No and orderID as composite key?
@drdread92657 жыл бұрын
really cool
@y4cministriesinternational9657 жыл бұрын
i like this thanks allot
@idrissnyanja53696 жыл бұрын
Sorry sir .once you are given to design an ERD of an organization or companies .and you want all departments to be represented by it table how do we count relation between the attribute (many to many) or (one to one) or (one to many)? Please sir help me
@md.imanali99984 жыл бұрын
Very helpful. thank you for making this video.
@GoodDeedsLeadTo Жыл бұрын
Oracle Database is a set of tables with foreign key primary key relationship and at the O/S level it is a file with dbf extension? & database server at the O/S level is a set of dbf and files with few other extensions?
@ydherdn4 жыл бұрын
Thank You
@PapaMufti3 жыл бұрын
I have hard time understanding the second version of the model. How is the address tied to customer ID? What specifically is the address attribute for? Street name, house number, flat number? How is this situation different from having customer name in one field as it is in the first model?
@harshilparmar90765 жыл бұрын
thanks brother
@RockstarGunner096 жыл бұрын
Shouldn't the CustomerID in CustomerPhone be a FK not a PK? Same as the OrderID and ProductID in the OrderProducts table?
@littleleaves98862 жыл бұрын
if we make them FK then we have to introduce their own ID like customerPhoneID, orderProductsID
@masulethomas45073 жыл бұрын
best example for bigginers
@malchicken4 жыл бұрын
Very clear. Thank you.
@ORACLEAPEX4103 жыл бұрын
nice video keep it up
@Bursadesain6 жыл бұрын
good content, thank you
@Bursadesain6 жыл бұрын
good video, thanks
@ciaranmckenna50347 жыл бұрын
Great work, if you have anymore examples please do share them. In your 3NF what exactly happened to the multiple values for phone numbers, if a customer had a work and home number what happened there?
@GoSparker7 жыл бұрын
Go to about 8:10 and the CustomerPhone table as a design option. There is a Type column that you can use to distinguish between work, home, cell, etc. The design could be expanded to have a Type table with TypeID and Type and then you would put TypeID in the CustomerPhone table rather than Type. This expanded design would help control and standardize the Type(s) that are used in the applications.
@HaploBartow7 жыл бұрын
Thanks for this comment; I feel like your description in the video did not explain the improvement very well, but this comment helps cover that gap.
@hajimunirsediqi14925 жыл бұрын
Hallo, i watched ur vedio , it is great thank u from ur teachng, want a database which is already created in postgresql , then i can fallow step by step. thank u
@taimurkhan84205 жыл бұрын
haji sahb turr jao
@zabihullahrezaei3616 жыл бұрын
may did you make a vedio for a ER diagram of computer Store.
@Mark4Jesus2 жыл бұрын
Thanks for this lesson. I wasn't clear on why 2 phone numbers is bad?
@kulkarnik16 жыл бұрын
Thanks for video. But I have a question. How can you say that customer table violates 2nf? I don't think it does because employer name is totally dependent on customer key and not the subset of the candidate key. Please let me know. Thanks!
@littleleaves98862 жыл бұрын
I agree with you. But if you need to keep full details of Employer, better move that to separate table.
@johnkelly89194 ай бұрын
No Address2 for unit, apartment or suite information or an address behind a street front building?
@mikeendsley84535 жыл бұрын
Great video! I would like to correct you on one thing @ 15:50... you are using PascalCase and not camelCase... notice the difference?
@GoSparker5 жыл бұрын
Pascal Case is a subset of Camel Case, which is the more widely known term (although Pascal Case could very well be more utilized in database naming). To be more complete with the various ways fields are often named: camelCase, PascalCase, snake_case, kebab-case ... but even within these there are variations and different types of requirements depending on many things including programming language and configuration of installation. One other point - many DBMS installs are not case sensitive by default. Could almost make a video just on naming conventions... thanks for bringing this up Mike.
@shreyasjejurkar12334 жыл бұрын
Yes it's PascalCase.
@zabihullahrezaei3616 жыл бұрын
very good
@AbdurRahim-ot5gp3 жыл бұрын
A problem occurred while Microsoft Access was communicating with the OLE server or ActiveX Control how to fix
@nathanunderbsd59725 жыл бұрын
why all PK there is no FK?
@arbabqaisar654 Жыл бұрын
Not all heroes wear capes
@NagimuKafeero11 ай бұрын
Wow thanks
@r2dclub696 жыл бұрын
nice video
@brandonmohammed22343 жыл бұрын
HELL IS REAL HEAVEN IS REAL GOD IS REAL JESUS IS THE SON OF GOD ALL THOSE WHO ARE NOT SAVED WILL GO TO HELL AND HELL IS TORTURE FOR ETERNITY BURNING IN NEVER ENDING FIRE, ONCE YOU ARE IN HELL THERE IS NO WAY OUT, HOWEVER RIGHT NOW IT IS POSSIBLE TO PREVENT YOURSELF FROM GOING TO HELL AND BECOMING SAVED AND THERE IS ONLY ONE WAY OUT AND THIS WAY IS JESUS, JESUS DIED AND ROSE AGAIN AS A SACRIFICE FOR OUR SINS SO THAT WE DON'T HAVE TO GO TO HELL AND WE CAN HAVE EVERLASTING LIFE SO WE CAN SPEND ETERNITY WITH HIM IN HEAVEN WHICH IS PURE PARADISE. ALL YOU HAVE TO DO IS TO PUT YOUR FAITH IN JESUS AND TRUST THAT HE WILL SAVE YOU AND THE HOLY SPIRIT WILL MAKE HIS HOME IN YOUR HEART AND LEAD YOU ON THE RIGHT PATH. DON'T DELAY IN TRUSTING JESUS BECAUSE WE CANNOT TELL WHEN IT IS TOO LATE. JESUS IS COMING SOON PLEASE BE READY AND MAKE THE RIGHT CHOICE
@nickfleming37195 жыл бұрын
So, lets say we have a local business where the # of zip codes is limited but you can have thousands of customers. Would it save memory and increase search speed to store the list of zip codes in a separate table and just have a zip_id field for each customer point to a row in the zip code table, instead of storing the whole zip code for each customer?
@GoSparker5 жыл бұрын
Preface this response with 'it depends', but in general you would be adding complexity. Consider looking at this another way - don't store city and use zip code to look up city. For a local business the volume is likely such that the space savings for having a zip lookup would be inconsequential. With regard to speed - adding joins can actually slow down queries so often the design question is balancing space and speed. In other words, saving space in a way that increases joins may slow down response time. So you often find that a gain in one (space) area is a loss in another (speed). Usually it is best to keep your design as simple and flexible as possible so that as it goes through its life cycle you are in a position to be able to adapt/modify the design for new requirements that emerge. A zip_id would likely be some type of integer field. The zip code may be an integer or character (international zip codes). So you would be adding an additional field with zip_id that probably consumes approximately the same space as zip code. You would also need to maintain a zip code table that may end up being all zip codes. So bottom line is unless there are unusual requirements I wouldn't create a zip_id field that points to zip code.
@JamesAutoDude2 жыл бұрын
I learned this too late after my database grew too much 😭 the struggle is real
@atultyagi49445 ай бұрын
perfect
@selimreza71638 жыл бұрын
next part plz
@santoshkumarkar394 жыл бұрын
Excellent... E.. X... C.. ellent..
@GoSparker4 жыл бұрын
Thank you Santosh!
@himanshumewari74257 жыл бұрын
can we use customer ID , Product Id in a single table?? of order ID
@taimurkhan84205 жыл бұрын
no
@granand3 жыл бұрын
Thank you .. Sir. Just on lighter note: :-) Sai Reddy .. 8342 Cricket as address :-) :- ) I come from same city Hyderabad and I confirm this is example not real data .. zip code there 6 digits?
@lukealadeen7836 Жыл бұрын
What about data lakes?
@cubiCampla5 жыл бұрын
epic
@Paretozen6 жыл бұрын
Why is Excel not a database? Even a piece of paper can be a database right?
@krissicura8426 жыл бұрын
No, a piece of paper is not a database. The easiest way for me to explain is to say that the data in an excel spreadsheet can be used BY a database to manipulate or manage that data, but it is not in and of itself a database. Think of a spreadsheet as being flat, again, like a sheet of paper but a database as being multi-dimensional. When you want a simple "list" a spreadsheet will do just fine, but as your needs grow and the data points begin to relate in different ways, you may need a database to organize and report on that data.
@mudaprince30672 жыл бұрын
i want to prepare supply chain project can you help me please
@aakashkumar70527 жыл бұрын
please any body give me a learning managment system ERD in database
@Skibadee99 Жыл бұрын
10:00 Customer DOB should be part of PK, not phone number as the number could change. Primary keys should not be updated
@GoSparker Жыл бұрын
If I understand your comment at 10 minutes, I'm describing the CustomerPhone table, where phone number is the main piece of data (with area cd). Utilizing DOB rather than phone number as the key would introduce a few potential challenges. One is that the same phone number could be attributed to multiple people. Another is that CustomerID is already unique, so adding DOB would provide no additional benefit as far as key structure in the context of this design. If a person's phone number changed you will create a new record in the CustomerPhone table. If the previous phone number was no longer valid then you would delete the record. You are correct in that primary keys normally don't change - but deleting and adding records is a common operation. If the CustomerPhone key was CustomerID and DOB then you basically have a one to one relationship with the Customer table. This would not allow additional phone numbers (many people have more than one) and then the Customer and CustomerPhone tables would be collapsed into one table as a one to one relationship is not normalized.
@Endoe.McKronic5 жыл бұрын
I fell asleep like 4 times.... Sheeeesh
@santoshkumarkar394 жыл бұрын
What is the software name...
@ChristopherJohnsonIsAwesome4 жыл бұрын
Microsoft Visio was the diagram tool and SQL Server Management Studio was the database tooling
@GoSparker4 жыл бұрын
@@ChristopherJohnsonIsAwesome Yes Santosh - Christopher is correct.
@nothanks8223 Жыл бұрын
👀
@roselpadilla2 жыл бұрын
Ferris State > hArVard
@valthalin76132 жыл бұрын
Data viz, because I'm dumb. customer: id=1(pk); fname=paul id=2(pk); fname=matt Products: id=16,(pk) name=sunglasses id=17(pk), name=Nintendo switch order: id=1(pk); customer_id=1, date=2021 id=2(pk); customer_id=2, date=2020 order_products: [order_id=1, product_id=16](pk); qty=1 "paul order 1 sunglasses" [order_id=1, product_id=, 17](pk); qty=1 - ON Conflict (set qty += 1) -- update qty for duplicate [order_id=1, product_id=, 17](pk); qty=1 + 1 "paul ordered 2 Nintendo switch" [order_id=2, product_id=, 17](pk); qty=1 "matt ordered 1 Nintendo switch"