Need solution for this question? 1) Composite and Multi-Valued Attributes Composite and multi-valued attributes can be nested to any number of levels. Suppose we want to design an attribute for a STUDENT entity type to keep track of previous college education. Such an attribute will have one entry to each college previously attended, and this entry is composed of: college name, start and end dates, degree entries (degrees awarded at that college, if any), and transcript entries (courses completed at that college, if any). Each degree entry is formed of degree name and the month and year it was awarded, and each transcript entry is formed of a course name, semester, year, and grade.

a. Design an attribute to hold this information (HINT: multi-valued attributes are shown between set braces { }.

Components of a composite attribute are shown between parentheses ( ).)

b. Draw the physical Schema (NOTE: in addition to the multi-valued attribute, the STUDENT entity has a StudentID and a StudentName)

2) Normalization Transform the following relation into 3NF. Make appropriate assumptions about functional dependencies and domains. State your assumptions.

INVOICE(InvoiceNumber, CustomerName, CustomerNumber, CustomerAddress, ItemNumber, ItemPrice, ItemQuantity, SalespersonNumber, SalespersonName, SubTotal, Tax, TotalDue)

3) SQL Queries on one relation (table)

The database table Student contains the following fields:

StudentID

StudentName

Address

City

State

Zip

Sex

a. List the entire record of all students with the name Jones.

b. List the entire record of all students whose Name begins with the letter S.

c. List the names, cities states and zip codes of all students whose zip codes are between 20000 and 29999 or who live in a city called Erie.

d. List the names and states of all students who are not from Nevada. e. List the names and home states of all students from states that begin with the letter C.