functional dependencies and normalization for relational dat, Database Management System

Consider the 1ollowin8 relation:
CAR SALE (Car_id, Option_type, Option_listprice, Sale_date, Option_discountedprice)
This relation refers to options installed in cars (e.g., cruise control) that were sold at a dealership, and the list and discounted prices of the options.

If CarlD Sale date and Option _typo Option_hstprica and CarlD, Option_type Option_discountedprice, argue using the generalized definition of the 3NF that this relation is not in 3Nf. Then argue from your knowledge of 2NF, why it is not even in 2NF.
Posted Date: 10/3/2012 1:38:18 PM | Location : United States







Related Discussions:- functional dependencies and normalization for relational dat, Assignment Help, Ask Question on functional dependencies and normalization for relational dat, Get Answer, Expert's Help, functional dependencies and normalization for relational dat Discussions

Write discussion on functional dependencies and normalization for relational dat
Your posts are moderated
Related Questions

What is Data dictionary? A data dictionary is a reserved space in a database that is employed to store information about the database itself. A data dictionary may consist o

Process of normalization is the integral part of designing a database. Justify this statement with suitable database design

What is Collation Collation is a kind of sort order. There are majorly 3 types of sort orders, namely: i.) Dictionary case insensitive ii.)Dictionary - case sensitive


What are the Issues when Selecting a Database Issues when Selecting a Database Storage space requirement: A database requires about triple storage space of the actua

Rearrange Classes and Operations Sometimes, the similar operation is defined across different classes and can easily be inherited from a familiar ancestor, but more often oper

Economics: It is now usually accepted that it costs less to make a system of smaller computers with the equivalent power of a one large computer. It is more cost-effective to get s

Backward Recovery (UNDO): In this system the uncommitted changes made by a transaction to a database are undone.  Instead the system is reset to the last consistent state of databa

Although, the essential features of E-R diagrams are enough to design many database situations. Though, with more difficult relations and advanced database applications, it is need