Machan ICT eke Database normalization eka wenne kohomada kiyala kiyanna puluwanda? Normalization eka karanna puluwan ekak nathuwa therenne na.

History - ICT

Piumi Hettiarachchi17 hours ago · Student

0 Helpful 12 answers Public question Public AI conversation

Community answers 12

Learn from each other

Chamara Wijesinghe 17 hours ago

Database normalization eka data redundancy (duplication) kam karala integrity ekak hadanna one. Meka relational database design eke fundamental concept ekak. Normalization process eken tables split karana, foreign keys use karana.
Pasindu Kumara 17 hours ago

ඔයාට තේරෙන්නෑ කියලා ආතල් වෙන්න එපා මචං. Normalization කියන්නේ Database එකේ redundancy (දත්ත නැවත නැවත ඇතුළු කිරීම) අවම කරල, data integrity එක රැකගන්න කරන ක්‍රමවේදයක්. මූලික Normal Forms (1NF, 2NF, 3NF) හොඳින් පුරුදු වෙන්න. ඒවායේ rules ගැන ලිස්ට් එකක් හදාගෙන practice කරන්න, ඉක්මනට තේරෙන දෙයක්.
Dilshan Kodikara 17 hours ago

Machan Database eke redundant data remove karanna, anomalies prevent karanna puluwan technique ekak normalization. Meeka tables split karala relationships primary keys use karala define karanna puluwan. Eka data integrity improve karanna help wenna.
Supuni Gamage (AI) 16 hours ago

Hi Supuni! Database normalization eka simple wela ekak nathuwa therenne. **Normalization** enawa database ekata **data redundancy (dubbar data)** one ganna, data integrity eke raksha karanne wade method ekak. Simple example ekak widiyata: Imagine you have a table called `Orders`: | OrderID | CustomerName | ProductName | Price | |---------|--------------|-------------|-------| | 1 | John | Laptop | 200 | | 2 | John | Mouse | 20 | | 3 | Sarah | Laptop | 200 | Here, "John" and "Laptop" data dubbar wela save vunuwe. If John's name changes, we have to update multiple rows. This is bad. **Normalization** widiyata this tables separate karanna: 1. **Customers Table:** | CustomerID | Name | |------------|------| | 1 | John | | 2 | Sarah | 2. **Products Table:** | ProductID | Name | Price | |-----------|--------|-------| | 1 | Laptop | 200 | | 2 | Mouse | 20 | 3. **Orders Table (just links):** | OrderID | CustomerID | ProductID | |---------|------------|-----------| | 1 | 1 | 1 | | 2 | 1 | 2 | | 3 | 2 | 1 | Now, if John's name changes, only one row in the Customers table updates. Much cleaner! Main goal: **Data consistency** & **Less storage**. 😊