1.Look up the definition of functional dependency. Can you find a good example? In relational database theory, a functional dependency is a constraint between two sets of attributes in a relation from a database. Cars
Suppose one is designing a system to track vehicles and the capacity of their engines. Each vehicle has a unique vehicle identification number (VIN). One would write VIN → Engine Capacity because it would be inappropriate for a vehicle's engine to have more than one capacity. (Assuming , in this case, that vehicles only have one engine.) Transversely, Engine Capacity → VIN is incorrect because there could be many vehicles with the same engine capacity. This functional dependency may suggest that the attribute Engine Capacity be placed in a relation with candidate key VIN. However, that may not always be appropriate. For example, if that functional dependency occurs as a result of the transitive functional dependencies VIN → Vehicl e Model and Vehicle Model → Engine Capacity then that would not result in a normalized relation. http://en.wikipedia.org/wiki/Transitive_dependency
2.Look up the definition of transitive dependency. Can you find a good example? In Database Management System, a transitive dependency is a functional dependency which holds by virtue of transitivity. A transitive dependency can occur only in a relation that has three or more attributes. Let A, B, and C designate three distinct attributes (or distinct collections of attributes) in the relation. Suppose all three of the following conditions hold: 1.A → B
2.It is not the case that B → A
3.B → C
Then the functional dependency A → C (which follows from 1 and 3 by the axiom of transitivity) is a transitive dependency. In database normalization, one of the important features of third normal form is that it excludes certain types of transitive dependencies. E.F. Codd, the inventor of the relational model, introduced the concepts of transitive dependence and third normal form in 1971.
A transitive dependency occurs in the following relation:
Twenty Thousand Leagues Under the Sea
Journey to the Center of the Earth
Leaves of Grass
3.Look up “denormalization” and provide information on why anyone would want to do it. In computing, denormalization is the process of attempting to optimize the read performance of a database by adding redundant data or by grouping data. In some cases, denormalization is a means of addressing performance or scalability in relational database software. A denormalized data model is not the same as a data model that has not been normalized, and denormalization should only take place after a satisfactory level of normalization has taken place and that any required constraints and/or rules have been created to deal with the inherent anomalies in the design. For example, all the relations are in third normal form and any relations with join and multi-valued dependencies are handled appropriately.
Examples of denormalization techniques include:
Materialised views, which may implement the following: Storing the count of the "many" objects in a one-to-many relationship as an attribute of the "one" relation Adding attributes to a relation from another relation with which it will be joined
Star schemas, which are also known as fact-dimension models and have been extended to snowflake schemas Prebuilt summarisation or OLAP cubes
Denormalization techniques are often used to improve the scalability of Web applications.