Consider the following database schema for music festival concerts. Underlined attributes denote a primary key. Only Genre can be NULL for any given tuple. FESTIVAL(FestivalName, FestivalID, Venue, StartDate, EndDate, Base TicketPrice) BAND(BANDNAME, BandID, Genre) PERFORMANCE (BID, FestID) And consider the following referential integrity constraint: For the PERFORMANCE relation, BID should reference a valid BandID in BAND, and FestID should reference a valid FestivalID in FESTIVAL. I. (60 pts) Write SQL data definitions to define appropriate table schemas for the festival concert database. Attribute domain choice is flexible, within reason (don't limit names or ids to a single character, for example). You do not need to write any code to add tuples to the database, and you can assume all the preliminary setup (Use command, etc.) before your data definition is already complete. II. (10 pts each) Write standard SQL queries to retrieve the following information from the database: a. List the band name and id of every band in the "Jazz" genre. b. List the festival name, venue, starting date, and ending date of every free festival. c. List the name of every festival at "KFC Yum! Center" that starts or ends in the year 2020. d. List every combination of band, by name, who has played (or is scheduled to play) at every venue. Each band, venue pair should be returned only once. To clarify potential confusion with query #4. if "The Miles Davis Quintet" played at five different individual festivals in Grant Park, Chicago, the pair ("Miles Davis Quintet", "Grant Park") should only be returned once by the query.