Introduction
In today's data-driven world, storing and managing information efficiently is crucial for businesses and organizations of a...
For further actions, you may consider blocking this person and/or reporting abuse
Wow. This might be the best post I've seen on here re: RDBMS. Seriously. Very comprehensive, well-written, and succinct at the same time. Kudos!
Thank you Dan, Really appreciate that
This is well done - compact and comprehensive! Nice things to possibly add:
Very nice suggestions, for sure I'll add them ASAP, Thank you very much Dan
Great post, thank you!
It's worth to mention that - depending on your data - other types of db could be used:
RDBMS can be very efficient, but setting up a data model can be challenging - especially if you are new to this topic. So, it's always good to know the different options and to select right one.
I don't think that a no-sql or document database is absolutely schema-free. Having a schema helps maintain consistency in the data structure and quality (validation).
Surely not, and finally you need to know the structure to work with your data. But because the Schema is driven by the data, it can be easily expanded. This makes validation much harder and in the worst case you fill your database with lot´s of useless data. So, you will need to do some schema-exploration and garbage collection working with the database.
As a main difference, the schema in an RDB is maintained by the database, while in a no-SQL db it is maintained by the supplier and consumer of data. The database is relative agnostic about the data it stores, which is a real paradigm shift. But it depends much on your task, it can be an advantage or a disadvantage.
that's more than what I can understand in one lecture (or 10🙂) , that was pretty direct and clear thank u for this explanation (You could have explained this all at class ; We wouldn't have died of boredom from BDD's teacher explanaition )
Thank you my biggest supporter ✨
Very clear and well explained 👏
In the 2NF, it was not the course_name column violating the rule ?
Absolutely true, the coure_name is the subject matter not the grade,
Corrected
Thank you very much flosej
Man i like your explaining method the information is stored directly in my database
Nicely done. A great refresher or solid beginning knowledge.
As always your articles are so pretty
-nice organization
-variety of informations
Congratulations 🎉🎉
Just Wow!!! That truly very well structured and in depth guide, thanks!
Thank you I really appreciate that
Great article for a revision you nailed it. You can look forward to entity sub type and super type in future.
This is very precise, simple. Good for an expert and for a total beginner.
Good post
Thank you for providing such valuable content.
Thank you for great post.
Can you please tell me when should I need to normalize in my DB.
Well, applying normalization on ur database schema design is tropically done, among the latest steps you do in the process, where after u define the entities, primary keys, foreign keys, indexes and refine the structure, you start applying the normalization rules up from 1NF to 2NF to 3NF.
Hope that clarified things a little.
Great post!
I liked how he/she explains everything in a simplified manner. Thanks !
Thank you for this exhaustive article! A truly wonderful read. I also learned something from this.
I never looked up the term "normalization". I've taken a bigger interest into looking up the definition of specific terms in our industry in recent year, as it is driven by them. To me the word "normalization" always sounded like a task, something that was done after you've built your database, to improve it's performance.
This article showed me that's actually not the case. It's actually a design principle.
It is a principle (or a set of principles) that I have (luckily) followed throughout my whole career. I've also gotten a bit better at it through practice over time. Since we're continuously applying those principles to our database design, we don't have complete the work later, when it's much harder.
So thank you for teaching me something!
Very well done! Very comprehensive!
Thanks. Well written article. Very clear, concise, well explained.
This could be the best interview recap about RDBMS.
That’s an excellent job! Very thourough and a great place to start someone the database journey. Keep up the good work!
noice!!
Nice post!
I just reviewed several details that were already rusty
I was just wonder:
What is the difference between
manyandzero-to-many+one-to-manyin ER diagrams.I felt as the first was contained in the both two
Terrific post! Thanks for sharing.
nice that 👌👌👌
Nice articles, really good! Thanks for sharing it!
Great one.
wow nice one
An indispensable resource for anyone seeking to build robust and efficient database systems. Reddy Anna Login
Great content. Thank you
Top!!!
Great post!