Project 1 SQL Views and Functions Please make sure you have submitted all the questions before: Fri 20 Apr, 5:00 pm 1. Aims This project aims to give you practice in • reading and understanding a moderately large relational schema (MyMyUNSW)• implementing SQL queries and views to satisfy requests for information• implementing SQL functions to aid in satisfying requests for information The goal is to build some useful data access operations on the MyMyUNSW database. A theme of this project is "dirty data". As I was building the database, using a collection of reports from UNSWs information systems and the database for the academic proposal system (MAPPS), I discovered that there were some inconsistencies in parts of the data (e.g. duplicate entries in the table for UNSW buildings, or students who were mentioned in the student data, but had no enrolment records, and, worse, enrolment records with marks and grades for students who did not exist in the student data). I removed most of these problems as I discovered them, but no doubt missed some. Some of the exercises below aim to uncover such anomalies; please explore the database and let me know if you find other anomalies. 2. How to do this project: • read this specification carefully and completely• familiarize yourself with the database schema (description, SQL schema, summary)• make a private directory for this project, and put a copy of the proj1.sql template there• you must use the create statements in proj1.sql when defining your solutions• look at the expected outputs in the expected_qX tables loaded as part of the check.sql file• solve each of the problems below, and put your completed solutions into proj1.sql • check that your solution is correct by verifying against the example outputs and by using the check_qX() functions • test that your proj1.sql file will load without error into a database containing just the original MyMyUNSW data • double-check that your proj1.sql file loads in a single pass into a database containing just the original MyMyUNSW data• submit the project via give. 3. Introduction All Universities require a significant information infrastructure in order to manage their affairs. This typically involves a large commercial DBMS installation. UNSWs student information system sits behind the MyUNSW web site. MyUNSW provides an interface to a PeopleSoft enterprise management system with an underlying Oracle database. This back-end system (Peoplesoft/Oracle) is often called NSS. UNSW has spent a considerable amount of money ($80M+) on the MyUNSW/NSS system, and it handles much of the educational administration plausibly well. Most people gripe about the quality of the MyUNSW interface, but the system does allow you to carry out most basic enrolment tasks online. Despite its successes, however, MyUNSW/NSS still has a number of deficiencies, including: • no waiting lists for course or class enrolment• no representation for degree program structures• poor integration with the UNSW Online Handbook The first point is inconvenient, since it means that enrolment into a full course or class becomes a sequence of trial-and-error attempts, hoping that somebody has dropped out just before you attempt to enrol and that no-one else has grabbed the available spot. The second point prevents MyUNSW/NSS from being used for three important operations that would be extremely helpful to students in managing their enrolment: • finding out how far they have progressed through their degree program, and what remains to be completed • checking what are their enrolment options for next semester (e.g. get a list of suggested courses) • determining when they have completed all of the requirements of their degree program and are eligible to graduate NSS contains data about student, courses, classes, pre-requisites, quotas, etc. but does not contain any representation of UNSWs degree program structures. Without such information in the NSS database, it is not possible to do any of the above three. So, in 2007 the COMP9311 class devised a data model that could represent program requirements and rules for UNSW degrees. This was built on top of an existing schema that represented all of the core NSS data (students, staff, courses, classes, etc.). The enhanced data model was named the MyMyUNSW schema. The MyMyUNSW database includes information that encompasses the functionality of NSS, the UNSW Online Handbook, and the CATS (room allocation) database. The MyMyUNSW data model, schema and database are described in a separate document. 4. Setting Up To install the MyMyUNSW database under your Grieg server, simply run the following two commands: $ createdb proj1
$ psql proj1 -f /home/cs9311/web/18s1/proj/proj1/mymyunsw.dump If youve already set up PLpgSQL in your template1 database, you will get one error message as the database starts to load: psql:mymyunsw.dump:NN: ERROR: language "plpgsql" already exists You can ignore this error message, but any other occurrence of ERROR during the load needs to be investigated. If everything proceeds correctly, the load output should look something like: SETSETSETSETSETpsql:mymyunsw.dump:NN: ERROR: language "plpgsql" already exists... if PLpgSQL is not already defined,... the above ERROR will be replaced by CREATE LANGUAGE SETSETSETCREATE TABLECREATE TABLE... a whole bunch of theseCREATE TABLEALTER TABLEALTER TABLE... a whole bunch of theseALTER TABLE Apart from possible messages relating to plpgsql, you should get no error messages. The database loading should take less than 60 seconds on Grieg, assuming that Grieg is not under heavy load. (If you leave your project until the last minute, loading the database on Grieg will be considerably slower, thus delaying your work even more. The solution: at least load the database Right Now, even if you dont start using it for a while.) (Note that the mymyunsw.dump file is 50MB in size; copying it under your home directory or your /srvr directory is not a good idea). If you have other large databases under your PostgreSQL server on Grieg or you have large files under your /srvr/YOU/ directory, it is possible that you will exhaust your Grieg disk quota. In particular, you will not be able to store two copies of the MyMyUNSW database under your Grieg server. The solution: remove any existing databases before loading your MyMyUNSW database. If you are running PostgreSQL at home, the file proj1.tar.gz contains copies of the files: mymyunsw.dump, proj1.sql to get you started. You can grab the check.sql separately, once it becomes available. If you copy proj1.tar.gz to your home computer, extract it, and perform. commands analogous to the above, you should have a copy of the MyMyUNSW database that you can use at home to do this project. A useful thing to do initially is to get a feeling for what data is actually there. This may help you understand the schema better, and will make the descriptions of the exercises easier to understand. Look at the schema. Ask some queries. Do it now. Examples ... $ psql proj1 ... PostgreSQL welcome stuff ... proj1=# \d... look at the schema ...proj1=# select * from Students;... look at the Students table ...proj1=# select p.unswid,p.name from People p join Students s on (p.id=s.id);... look at the names and UNSW ids of all students ...proj1=# select p.unswid,p.name,s.phone from People p join Staff s on (p.id=s.id);... look at the names, staff ids, and phone #s of all staff ...proj1=# select count(*) from Course_Enrolments;... how many course enrolment records ...proj1=# select * from dbpop();... how many records in all tables ... proj1=# select * from transcript(3197893);... transcript. for student with ID 3197893 ...proj1=# ... etc. etc. etc.proj1=# \q You will find that some tables (e.g. Books, Requirements, etc.) are currently unpopulated; their contents are not needed for this project. You will also find that there are a number of views and functions defined in the database (e.g. dbpop() and transcript() from above), which may or may not be useful in this project. Summary on Getting Started To set up your database for this project, run the following commands in the order supplied:$ createdb proj1 $ psql proj1 -f /home/cs9311/web/18s1/proj/proj1/mymyunsw.dump $ psql proj1 ... run some checks to make sure the database is ok $ mkdir Project1Directory... make a working directory for Project 1 $ cp /home/cs9311/web/18s1/proj/proj1/proj1.sql Project1Directory The only error messages produced by these commands should be those noted above. If you omit any of the steps, then things will not work as planned. Notes Read these before you start on the exercises: • the marks reflect the relative difficulty/length of each question• use the supplied proj1.sql template file for your work • you may define as many additional functions and views as you need, provided that (a) the definitions in proj1.sql are preserved, (b) you follow the requirements in each question on what you are allowed to define • make sure that your queries would work on any instance of the MyMyUNSW schema; dont customize them to work just on this database; we may test them on a different database instance • do not assume that any query will return just a single resu 0). Q10 (4 marks)The head of school would like to know the performance of students in a set of CSE subjects. Subjectsin this set have their subject codes starting with “COMP93” and are offered in every major semester(i.e., S1 and S2) in a given period (from 2003 (inclusive) to 2012 (inclusive)). To evaluate theperformance of students, the head of school requested to know the HD rate in every major semester inthe given period. The HD rate is defined as the number of students who have got HD(Course_enrolments.mark >= 85) / number of students who have actually received a mark (i.e.Course_enrolments.mark >= 0). Define an SQL viewQ10(code,name,year,s1_HD_rate,s2_HD_rate) that gives a list of subjects. Each tuplein the view should contain the following:l the subject code (Subject.code field) l the subject name (Subject.name field) l the year (Semesters.year field in the format of the last 2 digits (i.e., 12 for 2012)) l semester 1 HD rate as numeric(4,2) l semester 2 HD rate as numeric(4,2) Note: (1). We only consider the students who receive a mark for the course taken. You may use Course_enrolments.mark >= 0 to retrieve a list of valid students. (2). Use numeric (4,2) to restrict the precision of the ratios, and be careful about typecasting between integers and reals. (3). You may not be allowed to use Semesters.id values directly anywhere in your query (e.g., you may not refer to 07S1 as 146). Try to use symbolic name (e.g., ‘00S1’) to refer to any semester in your SQL. 6. Submission You can submit this project by doing the following: • Ensure that you are in the directory containing the file to be submitted.• Type “give cs9311 proj1 proj1.sql”• If you submit your project more than once, the last submission will replace the previous one • To prove successful submission, please take a screenshot as assignment submission manual shows and keep it by yourself. • If you have any problems in submissions, please email to . You can also ask questions about this project in our project we will answer your questions as soon as possible. The proj1.sql file should contain answers to all of the exercises for this project. It should be completely self-contained and able to load in a single pass, so that it can be auto-tested as follows: • a fresh copy of the MyMyUNSW database will be created (using the schema from mymyunsw.dump) • the data in this database may be different from the database that youre using for testing• a new check.sql file will be loaded (with expected results appropriate for the database)• the contents of your proj1.sql file will be loaded• each checking function will be executed and the results recorded Before you submit your solution, you should check that it will load correctly for testing by using something like the following operations: $ dropdb proj1 ... remove any existing DB$ createdb proj1 ... create an empty database $ psql proj1 -f /home/cs9311/web/18s1/proj/proj1/mymyunsw.dump ... load the MyMyUNSW schema and data $ psql proj1 -f /home/cs9311/web/18s1/proj/proj1/check.sql ... load the checking code$ psql proj1 -f proj1.sql ... load your solution$ psql proj1proj1=# select check_q1(); … check your solution to question1 … proj1=# select check_q5a(); … check your solution to question5a … proj1=# select check_q10(); … check your solution to question10 proj1=# select check_all(); … check all your solutions to q1-q10 Note: if your database contains any views or functions that are not available in a file somewhere, you should put them into a file before you drop the database. If your code does not load without errors, fix it and repeat the above until it does. You must ensure that your proj1.sql file will load correctly (i.e. it has no syntax errors and it contains all of your view definitions in the correct order). If I need to manually fix problems with your proj1.sql file in order to test it (e.g. change the order of some definitions), you will be fined via half of the mark penalty for each problem. 7. Late Submission Penalty 10% reduction for the 1st day, then 30% reduction.