Scribd
Upload
5 views

Relational Database Design - Group 6

Uploaded by

Dzey Arcel Saavedra
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
5 views

Relational Database Design - Group 6

Uploaded by

Dzey Arcel Saavedra
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 3

Relational Database Design

What is Relational Database Design?


Relational Database Design is like organizing information in a smart way. Imagine your data as pieces in a
puzzle, and this design is about putting those pieces in tables.

Key Points
• Tables: Think of them like sheets in a notebook, each for a specific type of information.
• Columns: These are the different sections in a table, like spaces for names, ages, or dates.
• Relationships: It's about showing how these tables are connected, like linking related information
together.
• The aim is to keep things neat and efficient, preventing the same info from being repeated. It helps in
finding information quickly and making sure everything stays accurate.
• So, in simple terms, relational database design is the method of arranging your data like a well-
organized book, making it easy to manage and use.

Meet the Database Superhero - DBMS


• DBMS (Database Management System)
• Think of DBMS as a superhero for our database.
• It's like a guardian that keeps our data safe, finds it when we need it, and makes sure only the right
folks can get to it.

Key Functions :
• Data Storage:
• Acts like a super-secure vault, keeping tons of data in order.
• Makes sure our information is safe, organized, and easy to grab.
• Data Retrieval:
• Works like a speedy search engine, getting specific info super quickly.
• Helps us find what we're looking for in a flash.
• Access Control:
• Plays the role of a gatekeeper, deciding who gets to see or change parts of the database.
• Adds a layer of security by letting only the right people access the data.

Why It Matters:
• Super important for businesses and apps dealing with lots of data.
• Boosts data security, keeps things organized, and makes information easy to use.

Database Normalization
• Think of normalization as tidying up a messy room in our database.
• It's about arranging information neatly, avoiding repetitions, and ensuring everything has its proper
place.
Normalization Levels:
1NF (First Normal Form):
Think of your data like a collection of unique items, not a mix of things bundled together.
Each piece of information should be atomic, meaning it can't be divided further. Just like how a single
item in your room should be something specific, not a mix of different things.
2NF (Second Normal Form):
Imagine you have a key, like a magic word that identifies a group of items.
Now, each piece of information should be related to the entire magic word, not just a part of it. It's like
organizing your belongings so that everything in a group is connected to the same idea or category.
3NF (Third Normal Form):
Taking it a bit further, let's imagine your key is super special, like the main key to your room.
Each piece of information should be directly linked to this super special key. No indirect connections.
This ensures that everything in your room is related directly to the most important thing – the main
key.

Benefits:
• Efficiency: A tidy database runs smoother.
• Clarity: It's easier to understand and work with.
• Less Mistakes: Avoids repeating the same things.]

DBMS Database Join


• Imagine you have two friends, each holding different pieces of information. Database joins are like
getting those puzzle pieces from both friends and putting them together.
• Today, we'll learn how to do this using INNER JOIN, LEFT JOIN, RIGHT JOIN, and FULL JOIN.

Database Join Types:


• INNER JOIN:
• Combining pieces where both datasets have matching parts.
• It shows only the pieces where there's a match in both sets of data.
• LEFT JOIN:
• Taking all the pieces from the primary dataset and matching them with the pieces from the secondary
dataset.
• Even if there's no match, you still keep all the pieces from the primary dataset.
• RIGHT JOIN:
• Similar to LEFT JOIN, but this time you take all the pieces from the secondary dataset and match them
with the pieces from the primary dataset.
• Pieces from the secondary dataset are kept, and unmatched pieces from the primary dataset are
included if any.
• FULL JOIN:
• Bringing together all the pieces from both datasets, whether they match or not.
• It shows all the pieces from both sets, filling in gaps with null if there's no match.
Why Joining Matters :
Helps us see a complete picture by combining information from different sources.
Useful for better understanding and making decisions with our data.

You might also like