Before developing a database solution, Eventbase had been using a spreadsheet to record basic information about events. A fragment of this spreadsheet is used in this question see Figure 5). The fragment shows the event id, the date of the event, what its called, where it will be held with details about the location capacity and accessibility, the event organiser and the contact number for the event organiser.

The company used the following relation as the template for the spreadsheet columns. Each row in the spreadsheet holds data about one event:

• Event (EventID, Date, Title, Location, Address, Capacity, AccessRestrictions, OrganiserName, ContactNumber)

The following rules are known to always hold between the attributes of the above relation:

1. A value of EventID uniquely determines a single Date value.

2. A value of EventID uniquely determines a single Title value.

3. A value of EventID uniquely determines a single Location value.

4. A value of EventID uniquely determines a single Capacity value.

5. A value of EventID uniquely determines a single Address value.

6. A value of EventID uniquely determines a single AccessRestrictions value.

7. A value of EventID uniquely determines a single OrganiserName value.

8. A value of EventID uniquely determines a single ContactNumber value.

9. A value of Location uniquely determines a single Capacity value.
10. A value of Location uniquely determines a single Address value.
11. A value of Location uniquely determines a single AccessRetrictions value.
12. A value of OrganiserName uniquely determines a single ContactNumber value.

A table of sample data representing the relation is shown in Figure 5.

Figure 5 The relation Event represented by a table of sample data

• a.

  • i.Using the data in Figure 5, and the uniquely determines rules 1-12, describe, with an example, how an update anomaly might arise.

  • ii.Briefly explain why Event is in first normal form.

  • iii.Briefly explain why Event is in second normal form.

  • iv.Event is not in third normal form. Identify what prevents Event being in third normal form and then split the relevant attributes into new tables so that the resulting tables are in third normal form.

Address Location Park Lane Contact Number 00123 382112 11 Rustic Town Eventi Date Title E00282 10/09/22 Proms in the Park E00275 1/09/22 Stars by Starlight E00271 1/08/22 Twilight Tales Capacity AccessRestrictions Organisername 250 Fully accessible. Parker Promotions 300 Fully accessible. Bugle industries 555 12381 Haven Field Lakeside Manor 10, Half-acre Wood 18, The Lake 145 555 12381 E00283 10/09/22 Tea at Tall Tall Trees Windy Lane Trees 60 00123 382112 E00284 11/09/22 Proms by the Lake 18, The Lake 145 Long steep path to Bugle industries lakeside. Site vehicle available to assist. Disabled access to Parker carpark at side of Promotions site. Long steep path to Oscorp events lakeside. Site vehicle available to assist. Fully accessible. Parker Promotions Fully accessible. Bugle industries Lakeside Manor 00551 99231 250 00123 382112 300 E00285 14/06/22 Tea Dance Park Lane 11 Rustic Town in the Park E00290 15/09/22 Stars by Haven 10, Half-acre Starlight Field Wood E00291 17/09/22 Proms by Lakeside 18, The Lake the Lake 555 12381 145 555 12381 Manor Long steep path to Bugle industries lakeside. Site vehicle available to assist