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 a 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 us ...

1. 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
a 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

2. 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

3. 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

4. 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

5. 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

6. (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
Project 1
Identify and describe the entities and their attributes.
Movies: This entity stores all the information related to Movies
that are available in the Store.

7. Movie has following attributes:
MovieID - Unique id of the movie that are available in our
store.
MovieTitle - Title of the movie.
Duration - Length of the movie.
Rating – Rating of the movie.
YearReleased – Year in which movie is released.
MovieTypeID – Stores Category of the movie.
Customers: This entity stores information related to the
customer of that store.
Customer has following attributes:
CustomerID – Unique id of the customer that are using our
services.
CustomerName – Name of the customer.
StreetAddress – Address of the customer.
PostalCode - Postal Code of the customer.
Phone - Phone number of the customer.
Distributors: This entity stores distributor details.
Distributor entity has following attributes:
DistributorID – Unique id of the distributor.
DistributorName – Name of the distributor.
PhoneNo – Phone Number of the distributor.
Address – Address of the distributor.
DVDVideos: This entity stores list of all movies format
available.
DVDVideos entity has following attributes:
DVDVideoID – Unique identification number of video or DVD.
MovieFormat – Format of the movie i.e DVD or Video.
Price: Price of that video or DVD.
MovieID: Movie of that video or DVD.
DistributorID: Distributor of that video or DVD.
Rentals: This entity stores all movies that are rented out.

8. Rentals entity has following attributes:
RentID - Unique id of each movie that is rented out.
CheckOutDate – Date on which movie is rented out.
CheckInDate – Date in which that movie is returned.
LateFee – Fee if movie is not returned on time.
DamageFee – Fee if movie is damaged.
Taxes – Taxes applicable.
CustomerID – Customer that rented out.
DVDVideoID – DVD or video that is rented out.
DealsIn: This entity stores type of movies that distributor deals
in.
DealsIn entity has following attributes:
DistributorID – Id of the distributor.
MovieTypeID – Type of movie it deals in.
MovieType: This entity stores categories of movies.
MovieType entity has following attributes:
MovieTypeID – Unique id of movie category.
MovieType – Description of movie category.
MovieActors: This entity stores part actor played in each movie.
MovieActors entity has following attributes:
MovieID – Id of the movie
ActorID – Id of the actor.
Role – Roles actor plays in movies.
Actors: This entity stores information of the actors.
Actors entity has following attributes:
ActorID – Unique id of the actor.
ActorName – Name of the actor.
Age – Age of the actor.
Gender – Gender of the actor.
Directors: This entity stores information of the directors.
Directors entity has following attributes:
DirectorID – Unique id of the director.

9. DirectorName – Name of the director.
Gender – Gender of the director.
MovieDirectors: This entity stores information of who directed
that movie.
MovieDirectors entity has following attributes:
MovieID – Id of the movie.
DirectorID – Id of the director.
Awards: This entity stores information of the awards.
Awards entity has following attributes:
AwardID – Unique id of the awards.
AwardTitle – Title of that award.
Description – Description of that award.
AwardsWon: This entity stores information of awards won by
the movie.
AwardsWon entity has following attributes:
MovieID – Id of the movie.
AwardID – Id of the award.
YearWon – Year that award is won.
Develop relationship sentence pairs.
RENTALS - CUSTOMER
· Each RENTAL includes a CUSTOMER
· Each CUSTOMER may be involved in one or more RENTALS.
RENTALS - DVDVideos
· Each RENTAL includes a video or a DVD
· Each VIDEO may be involved in one or more RENTALS
MOVIES - DVDVideos
· Each MOVIE can have one or more video or a DVD
· Each VIDEO is related with one MOVIE.
MOVIES - MOVIETYPE
· Each MOVIETYPE can have one or more MOVIES
· Each MOVIE is related to at least one MOVIETYPE

10. MOVIE –ACTORS
· Each MOVIE can have one or more ACTORS
· ACTOR can works in multiple MOVIES
MOVIE –DIRECTORS
· Each MOVIE can have one or more DIRECTORS
· DIRECTORS can direct one or more MOVIES
MOVIE –AWARDS
· Each MOVIE can have one or more AWARDS
· AWARD can be given to multiple MOVIES
Mom and Pop Johnson Video Store Database E/R Diagram:
Proposed Database Tables and Columns based on E/R Diagram.
Movies
Field Name
Data Type
Length
Null
Primary Key
Foreign Key

11. MovieID
Integer
N
Y
MovieTitle
VarChar
40
Duration
integer
Rating
integer
YearReleased
Integer
MovieTypeID
Integer
Y

12. Customers
Field Name
Data Type
Length
Null
Primary Key
Foreign Key
CustomerID
Integer
N
Y
CustomerName
VarChar
25
StreetAddress
VarChar
100
PostalCode
VarChar
5
Phone
VarChar
15

13. Distributors
Field Name
Data Type
Length
Null
Primary Key
Foreign Key
DistributorID
Integer
N
Y
DistributorName
VarChar
25
PhoneNo
VarChar
15
Address
VarChar
100
DVDVideos

14. Field Name
Data Type
Length
Null
Primary Key
Foreign Key
DVDVideoID
Integer
N
Y
MovieFormat
VarChar
12
Price
Integer
MovieID
Integer
Y
DistributorID
Integer
Y

15. Rentals
Field Name
Data Type
Length
Null
Primary Key
Foreign Key
RentID
Integer
N
Y
CheckOutDate
Date
CheckInDate
Date
LateFee
Integer
DamageFee
Integer

16. Taxes
Integer
CustomerID
Integer
Y
DVDVideoID
Integer
Y
DealsIn
Field Name
Data Type
Length
Null
Primary Key
Foreign Key
DistributorID
Integer
N
Y
Y
MovieTypeID
Integer

17. N
Y
Y
MovieType
Field Name
Data Type
Length
Null
Primary Key
Foreign Key
MovieTypeID
Integer
N
Y
MovieType
VarChar
20
Actors
Field Name
Data Type
Length
Null
Primary Key
Foreign Key
ActorID
Integer
N

18. Y
ActorName
VarChar
20
Age
Integer
Gender
VarChar
1
MovieActors
Field Name
Data Type
Length
Null
Primary Key
Foreign Key
MovieID
Integer
N
Y
Y
ActorID
Integer

19. N
Y
Y
Role
VarChar
10
Directors
Field Name
Data Type
Length
Null
Primary Key
Foreign Key
DirectorID
Integer
N
Y
DirectorName
VarChar
20
Gender
VarChar
1

20. MovieDirectors
Field Name
Data Type
Length
Null
Primary Key
Foreign Key
MovieID
Integer
N
Y
Y
DirectorID
Integer
N
Y
Y
Awards
Field Name
Data Type
Length
Null
Primary Key
Foreign Key
AwardID
Integer
10
N
Y
AwardTitle
VarChar

21. 20
Description
VarChar
100
AwardsWon
Field Name
Data Type
Length
Null
Primary Key
Foreign Key
MovieID
Integer
N
Y
Y
AwardID
Integer
N
Y
Y
YearWon
Integer

22. Project 1
This project allows students to demonstrate their skills in the
area of designing relational databases to satisfy specific
business rules and requirements. The deliverables for this
project include an Entity Relationship Diagram and detailed
documentation describing the database design and structure.
Project 1 Details:
In this project you will be provided a set of specifications to
create an entity-relationship diagram and design accompanying
table layout using sound relational modeling concepts and
practices. The relationships between the entities and the
attributes for the entities will be identified and described. This
database will provide the foundation for the follow-on project.
The following paragraphs provide the background and summary
of the business requirements.
You are a database consultant with Ace Software, Inc. and have
been assigned to develop a database for the Mom and Pop
Johnson video store in town. Mom and Pop have been keeping
their records of videos and DVDs purchased from distributors
and rented to customers in stacks of invoices and piles of rental
forms for years. They have finally decided to automate their
record keeping with a relational database.
You sit down with Mom and Pop to discuss their business, and
watch their operation for about a week. You discover quickly
that a video and a DVD are both copies of a movie kept in a
separate plastic case that is rented out. They have several copies
of each movie they rent; therefore there are several videos and
DVDs for each movie title. You learn that in their inventory
they have several thousand videos and DVDs, which they get
wholesale from about a half dozen distributors. The video and

23. DVD prices to them are based on the quantity of their shipment
and the past business they have done with each company.
The price of a DVD for a movie might be different than the
price of a video for the same movie, even from the
same distributor. Each distributor provides different types of
movies (e.g., suspense, horror, mystery, comedy, etc.). A single
distributor may provide several different types of movies in
both video and DVD format. It is possible to obtain the same
movie from multiple distributors, and at different wholesale
prices.
Each video and DVD has a unique identification number that
Mom and Pop assign in their inventory, in addition to the
distributor's serial number for the item. Each movie also has a
unique identification number Mom and Pop assign in addition to
the title, and any movie IDs the distributors use in their
electronic catalogs. Distributors provide electronic catalogs to
Mom and Pop and the information from these catalogs must
be included in the database.
Mom and Pop need to record when a video or DVD is rented,
when a video or DVD is returned, and all customer charges such
as late and damaged fees, failure to rewind fees, and taxes.
They need a report of which videos are returned late because
there are standard and late charges. On occasion there are
discount prices for certain movies or types of movies.
Customers want to rent movies based on actors or actresses,
running length, type of movie, rating, year released, the
director, and the academy awards won (by the movie, the actors,
the actresses and/or the directors). Customers also want to know
how many videos they have rented in the last month, year, and
so forth. Mom and Pop need to keep only basic information on
customers in their database, such as name, address, telephone
numbers, etc.

24. There must be no limit to the number of video and/or DVD
copies of a movie that Mom and Pop can have in their
inventory. Video/DVD ID numbers, movie ID numbers, and
distributor ID numbers for videos, DVDs, and movies are all
different. Also, each movie must be able to have an unlimited
number of actors, actresses, directors, and academy awards (i.e.,
Oscars). Other types of awards (e.g., Golden Globe, People's
Choice, etc.) are not of interest for this application. The rental
of equipment, sale of videos, DVDs, popcorn, etc., is not to be
kept in the database.
Using this information, you should:
1. Determine and list your entities. Then describe fully the
relationships between entities via pairs of sentences that
indicate the two components of the total relationship in both
directions between the entities. Relationships may be unary,
binary, or ternary with respect to entities. You should not have
any many-to-many relationships.
2. Begin the database logical design by identifying the entities,
relationships between entities, and entities' attributes as we
have done in this course. Use the same entity/relationship
diagram (ERD) notation as used in class for entities, attributes,
and relationships. Sketch your ERD by hand or a drawing
program (e.g., Visio, PPT, SQL Modeler …) on one single 8-
1/2" x 11" page (8-1/2" x 14" maximum), labeled "Mom and
Pop Johnson Video Store Database E/R Diagram." Your ERD
should not have any many-to-many relationships between
entities. Make sure that all relationships between entities are
one-to-many to facilitate the construction of relational database
tables.
3. Complete the logical database design and start the physical
database design by creating metadata (i.e. documentation) that
describes the table(s) created from each entity and the
column(s) created from each attribute in the ERD. Attributes
should be self-describing.Particular attention will be given to
the proper specification of all primary key (via "PK") and

25. foreign key (via "FK") columns in the table layouts. These
should match your ERD exactly. Begin these descriptions on a
page labeled "Proposed Database Tables and Columns based on
E/R Diagram." All tables must be 3rd Normal Form. Indicate
any and all assumptions that were made.
4. Make sure your work is neat and legible.
5. Follow the procedures in the course modules and the
Database Development Phases document for
this project.
Submissions:
1. You should submit a well-organized Word document that
includes your entity list, ERD, and database design description.
This document should also include all assumptions and your
lesson learned during your project. Name you project
XXX_PROJECT1.doc(x) where XXX are your initials.
2. Submit document to LEO Project 1 area before the due
date. Please contact the instructor before the due date if you
have any questions or concerns.
Grading:
This activity is awarded 25% of the total grade in the course. In
the gradebook, the total number of points will be set to 100. The
project elements are assessed as follows:
Attributes
Value
Project Design
30 points
Project Functionality
40 points
Documentation
25 points

26. Documentation grammar and spelling
5 points
Total
100 points