Database Normalization 設計問題

本帖最後由 manpaul 於 2013-5-18 03:05 編輯

在設計關於Customer Order Databse Normalization時,遇上以上問題:
1. 會否對於Derived Attribute開一個Field來儲存其資料呢?(因應咩情況而用)
2. 2NF與3NF的關係是什麼?
3. 假如 Customer may have optionally membership, A Customer can followed by the consultant.
MemberID is unique key? 如果係又如何在Normailization表達呢?
3NF
Order (OrderID, CustomerID, EmployeeID, InvoiceID)
OrderProduct (OrderID, ProductID, Quantity, Integration, Amount)
Product (ProductID, ProductName, UnitPrice, DiscountPrice)
Customer (CustomerID, CustomerName, CustomerPhoneNo, CustomerAddress, MemberID)
Member (MemberID, MemberLastIntegration, MemberIntegrationGained, MemberIntegrationUsed, MemberLatestIntegration)
Employee (EmployeeID, EmployeeName, EmployeePhoneNo, CustomerID)
唔知呢個數據庫是否岩要設計的情況?
4. 我見有d Order / Invoice 例子,OrderNO / InvoiceNO Primary Key is "A0123456",應否使用這種設計?