The SQL ‘CREATE TABLE' scripts for all the tables you have implemented. Note that your tables must correspond exactly to the ERD you have provided in 1. above, or you will lose marks. Include also any ALTER TABLE scripts you have used to add constraints to your tables, if you have declared them separately.

SQL ‘INSERT INTO tablename' scripts for each of your tables, showing the sample data you have inserted into your database. The data should fully test the functionality of the system, as illustrated by your SQL queries.

SQL ‘CREATE VIEW' statement for the view you have implemented.Provide also an explanation and rationale for this view: (ie who will use it, what is it for, what does it show);

For each of your 8 SQL queries, provide a) an explanation/rationale for your view (what does it show, what is it for? Who will use it?) and b) the SQL script for your query.You should produce queries that fulfil realistic case study requirements and best demonstrate your knowledge of SQL. Assume also that you have tables populated with realistic numbers of records - so very rarely, IF EVER, will you want to run a SELECT * FROM table query. You should use ‘&prompts' where appropriate to make the queries more flexible; you must also order your output. A query which produces screens of unordered output is of no use to anyone.Remember the basics: output needs to be tailored to who is using it - management will require aggregated data, operational staff detailed records etc., etc.

For each procedure/trigger, provide a) an explanation of what the code does, and b) the PL/SQL script. Note: choose triggers/procedures that best demonstrate your understanding of PL/SQL and are relevant to the case study - ie they implement a stated business rule or requirement.