CMIS 320 Project 2





 




Project 2




Instructions:


 




In this
project you will perform the physical design and
implementation using SQL Data Definition Language (DDL) and proceed with populating the
Mom and Pop Johnson Video Store database via Data Manipulation Language (DML)
SQL commands.
Each of
the steps below requires a SPOOL file to be submitted.  Be sure your
SPOOL file contains your SQL statements along with the Oracle responses
and/or displayed results.  Do NOT submit your SQL script files. 
Only submit your output SPOOL files.  If you are using iSQL*Plus you
must screen snapshots as necessary of your SQL and the results.
Project
2 Details:


  1. Create Oracle database tables using SQL Data
    Definition Language (DDL) for each table listed in Project 1.  Make
    sure that entity and referential integrity are enforced by declaring
    primary key for each table (these
    may be composite keys) and declaring all appropriate foreign keys.
    Your CREATE TABLE statements must show integrity constraints, as
    appropriate, for NOT NULL, UNIQUE, PRIMARY KEY, FOREIGN KEY, REFERENCES,
    and CHECK constraints. Be sure to save your script used to create these
    tables as yournameproject2step1.sql. You should test your script to make
    sure it runs without error.  Submit your SPOOL file showing that
    all SQL in your SQL script file worked properly.

  2. Provide two examples of SQL
    DML (i.e., "INSERT") commands that fail different table
    integrity constraints you set up in one of your table. Explain why the
    statements fail. Be sure to save your script used to as yournameproject2step2.sql.
    You can include comments in the SQL script describing why the insert
    statements failed.    Submit your SPOOL file showing that
    all SQL in your SQL script file worked properly.

  3. Populate each of your tables
    with at least five valid rows of data each and show the
    SQL you used. Populate other tables in your database, as necessary, to
    satisfy referential integrity. Be sure to save your script used to
    create these records as yournameproject2step3.sql. You should test your
    script to make sure it runs without error.    Submit your
    SPOOL file showing that all SQL in your SQL script file worked properly.

  4. Write SQL to perform the
    following queries and updates. Be sure to save your script used to
    create these records as yournameproject2step4.sql. You should test your
    script to make sure it runs without error:




    • Retrieve all of your
      customers' names, account numbers, and addresses (street and zip code
      only), sorted by account number.

    • Retrieve all of the videos
      rented in the last 30 days and sort in chronological rental date order.

    • Produce a list of your
      distributors and all their information sorted in order by company name.

    • Update a customer name to
      change their maiden names to married names. You can choose which row to
      update.  Make sure that you use the primary key column in your
      WHERE clause to affect only a specific row.

    • Delete customers from the
      database. You can choose which row to delete. Make sure that you
      use the primary key column in your WHERE clause to affect only a
      specific row.



Submit
your SPOOL file(s) showing that all SQL in your SQL script file worked
properly.  Show the actual SQL statements executed and the results the
SQL produced below the code.  Do NOT submit your SQL script files. Also,
submit all of your .sql files.


 






Criteria


Exceeds


Meets


Does Not Meet




Creates


25 points




(23-25)
Tables
prepared with additional constraints beyond the requirements to enhance
data integrity
Correct
Syntax used all of the time
SQL
scripts prepared and comprehensively tested


22
points




(17-22)
Tables
prepared with all needed constraints
Correct
Syntax used all of the time
SQL
scripts prepared and tested


0
points




(0-16)
Many
errors in the Create table scripts
Constraints
rarely used.




Inserts


25
points




(23-25)
Excellent, efficient SQL insert statements addressing all
functionality
Statement is designed well, clear and neatly formatted
Commits included
No integrity constraint violations


22
points




(17-22)
Good SQL insert statements addressing most functionality
Statement has a good design but could be clearer or better
formatted
Commits included
Minor integrity constraint violations may be present


0
points




(0-16)
Poor SQL insert statements minimally addressing the
functionality
Poor design and formatting
Commits not included
Major integrity constraint violations presented




Selects


30
points




(27-30)
Excellent, efficient SQL select statements
addressing all functionality
Statement is designed well, clear and neatly
formatted
Multi-table joins are efficient using
correct syntax
Excellent clean and well-organized output display


26
points




(18-26)
Good SQL select statements addressing most functionality
Statement has a good design but could be clearer of better
formatted
Multi-table joins are reasonable but may include some
non-standard syntax or inefficiencies.
Good output display but could provide minor areas difficult to
follow


0
points




(0-17)
Poor
SQL insert statements minimally addressing the functionality
Poor design and formatting
Multi-table joins are mostly incorrect
Output display missing or of poor quality




Updates


10
points




(9-10)
Excellent, efficient SQL update statements
addressing all functionality
Statement is designed well, clear and neatly
formatted
Commits included
No integrity constraint violations


8
points




(7-8)
Good SQL update statements addressing most functionality
Statement has a good design but could be clearer or better
formatted
Commits included
Minor integrity constraint violations may be present


0
points




(0-6)
Poor SQL update statements minimally addressing the functionality
Poor design and formatting
Commits not included
Major integrity constraint violations present




Deletes


10
points




(8-10)
Excellent, efficient SQL delete statements addressing all
functionality
Statement is designed well, clear and neatly formatted
Commits included
No integrity constraint violations


8
points




(7-8)
Good SQL delete statements addressing most functionality
Statement has a good design but could be clearer or better
formatted
Commits included
Minor integrity constraint violations may be present


0
points




(0-6)
Poor SQL delete statements minimally addressing the
functionality
Poor design and formatting
Commits not included
Major integrity constraint violations present




Overall Score


Exceeds

90 or more



Meets

70 or more



Does Not Meet

0 or more














Bottom of Form









 
Powered by