Write the relational schema, draw its dependency diagram and identify all deper all partial and transitive dependencies. You can assume that the table does not groups and that any invoice number may reference more than one product. (Hin composite primary key.)

Create a Star Schema ERD for the Bob’s Fixit case study. Create the tables (create table DDL) from your Star Schema ERD.   Bob would like to know the following: The bid dollar amount by the customer zip code and customer state. The bid dollar amount by the bid month and bid year.

Indicate dependences and their type.

Suppose that A and B are two sets of entities connected by a relation R that has multiple one-to-one occurrences (see Figure 1). Think about a scenario in which R's generated connection is coupled with A's. SQL allows null values for attributes that are a part of a foreign key constraint. Give an example of how non-null constraints may be used in SQL to place a restriction on how much A can be involved in R.

Given the sample records in the CHARTER table shown in Table P6.11, do the following:a. Write the relational schema and draw the dependency diagram for the table structure. Make sure that you label all dependencies. CHAR_PAX indicates the number of passengers carried. The CHAR_MILES entry is based on round-trip miles, including pickup points. (Hint: Look at the data values to determine the nature of the relationships. For example, note that employee Melton has flown two charter trips as pilot and one trip as copilot.)b. Decompose the dependency diagram you drew to solve Problem 11a to create table structures that are in 3NF and write the relational schema.c. Draw the Crow's Foot ERD to reflect the properly decomposed dependency diagrams you created in Problem 11b. Make sure the ERD yields a database that can track all of the data shown in Problem 11. Show all entities, relationships, connectivities, optionalities, and cardinalities.To upload and submit your assignment, click the Choose…

Explain the role of functional dependencies and candidate keys in normalization.