Hey Guys, I need help on an ERD normalization question. from 1NF to 3NF?
Hey I have two questions on normalization that I am practicing for my final but I cant seem to get them.
This is in the 1st normal form and I need to get it to the 3rd normal form.
1.
Customer( CustomerID, Name, Address)
Product(ProductID, Description)
Order(Order Number, Customer ID, OrderDate)
LineItem(OrderNumber, ProductID, OrderQuantity)
Invoice(InvoiceNumber, OrderNumber, InvoiceDate)
Shipment(InvoiceNumber,ProductID,Quant…

2.
Vendor(VendorID,Address)
PriceOuote(QuoteQuantity,Price)
Part(itemNumber, Description)
PartReceipt(OrderNumber,Date,OrderQuan…

I did them but I am not sure if they are correct.
I need someone to help me get these to the 3rd NF from 1stNF.
Thanks to all you guys out there.
Any input is valued.

if you are unsure about normalisation then have a look at
Fundamentals of Relational Database Design -- r937.com
or
The Relational Data Model, Normalisation and effective Database Design

Hey, thanks for the information posted.
I read them and am still in the same place.
i did the work already.
I just need someone to do it so that I can check it with my work and see if I am on the right track.
With the other example, they are kinda small ones, and this one is a big one. I just want to see if I am doing it correctly.
Plz Help and Thanks

They look in 3NF already to me.

Are they correct? Couldn't a customer have multiple addresses? Same with a vendor?
Dave

PriceQuote looks incomplete, shouldn't it reference the item it is quoting a price for?

Perhaps, however that isn't normalisation but requirements.

Hello Friends.......

Normalization is the process of efficiently organizing data in a database. There are two goals of the normalization process: eliminating redundant data and ensuring data dependencies make sense

Thanks

unfortunately this is wrong, eliminating redundant data is ~not~ a goal of normalization

Normalization is a set of tools for analysing and eliminating certain types of redundancy. It cannot eliminate redundant data entirely. I doubt that any formal process ever could ensure non redundancy in all possible cases.

No normalization procedure can ensure that the dependencies "make sense" because a set of (assumed to be correct) dependencies are a necessary input for normalization, not the product of it. Some dependencies may be eliminated by normalization but unfortunately that doesn't mean the set of dependencies at the end are the right ones to do the job the database was intended for