Consider the following relations Carsale carno datesold salemanno commissiondiscount Assume a car can be sold by multiple salesman and hence primary key is car no salesman additional dependencies are Date sold discount and salesmanno Commission Database Management Systems 10CS54 VTU notes JAN 2014

The Eduladder is a community of students, teachers, and programmers just interested to make you pass any exams. So we solve previous year question papers for you.
Watch related videos of your favorite subject.
Connect with students from different parts of the world.
See Our team
Wondering how we keep quality?
Got unsolved questions?

Database-Management-Systems---10CS54-VTU-notes-->View question

Taged users:

Likes:
Be first to like this question

Dislikes:
Be first to dislike this question

### Watch more videos from this user Here

Learn how to upload a video and start earning here

Normalization is a process of achieving good database design. A database design needs some refinement which is achieved through normalization. Complex relations are decomposed into simpler relation using normalizations. Normalization is also used to check quality of database design. There are three levels of normalization. In a given relation R A and B are attributes, B is functionally dependent on A, and each value of A determines exactly one value of B.

i. 1NF

The relational schema R is in 1NF if an only if:

• All attributes or R are atomic in nature.
• All non-key attributes should be functionally dependent on key attribute.

ii. 2NF

The relational schema R is in 2NF if an only if:

• R is already in 1NF.
• There is no partial dependency in R which exists between non-key and key attributes.

iii. 3NF

The relational schema R is in 3NF if an only if:

• R is already in 3NF.
• There is no transitive dependency which exists between key and non-key attributes through another non-key attributes.

2. Explanation:

i. Since all attribute values are single atomic, the given relation CAR-SALE is in 1NF.

ii. Salesman# → commission% …Given

Thus, it is not fully functionally dependent on the primary key {Car#, Salesman#}. Hence, it is not in 2 NF.

The 2 NF decomposition for this relation is:

• CAR_SALE1(Car#, Salesman#, DateSold, DiscountAmount)
• CAR_SALE2(Salesman#, Commission%)

iii. The given relationship is not in 3NF because there exists a transitive dependency in the form

DiscountAmount → DateSold → (Car#, Salesman#)

Thus, DateSold is neither a key itself nor a subset of a key and DiscountAmount is not a prime attribute.

The 3 NF decomposition are as follows:

• CAR_SALES1A(Car#, Salesman#, DateSold)
• CAR_SALES1B(DateSold, DiscountAmount)
• CAR_SALE3(Salesman#, Commission%)

Likes:
|PrashantIIST

Dislikes:
Be first to dislike this answer

### Watch more videos from this user Here

Learn how to upload a video and start earning here

Lets together make the web is a better place

We made eduladder by keeping the ideology of building a supermarket of all the educational material available under one roof. We are doing it with the help of individual contributors like you, interns and employees. So the resources you are looking for can be easily available and accessible also with the freedom of remix reuse and reshare our content under the terms of creative commons license with attribution required close.

You can also contribute to our vision of "Helping student to pass any exams" with these.