Week 5 iLab Complete Solution

Question: #965

SQL script file named LastName_Lab3.sql. Word document named LastName_Lab3_Output. When you are done, zip up these files and submit them to the Week 5: iLab Dropbox.
Required Software
Omnymbus – MySQL
Access the software at https://devry.edupe.net:8300.
Steps 1–8
iLAB STEPS

STEP 1: Entity Relationship Diagram Analysis
Back to Top
Review the ERD below to understand the entities, attributes, primary keys, and relationships that you will create in your MySQL database.

STEP 2: Open MySQL via Omnymbus, Create SQL File, Drop Table
Back to Top
•To reference, learn and apply MySQL’s own dialect of the SQL language to this iLab, browse through the file M10C_KROE8352_13_SE_WC10C.pdf in the Doc Sharing folder titled My SQL Documents.
•Create a script file named LastName_Lab3.sql containing SQL statements created in Steps 3–7 below.
•Include DROP TABLE statements at the beginning of the SQL script file to ensure that tables are dropped when executing SQL script repeatedly. The following is an example of a DROP TABLE statement in MySQL;
SET FOREIGN_KEY_CHECKS=0; DROP TABLE tablename; (list all tables in database) SET FOREIGN_KEY_CHECKS=1;

STEP 3: Add Tables, Set Primary Keys and Foreign Keys
Back to Top
Add tables to the MySQL database.
•Add a table for each entity listed in the provided ERD diagram.
•Add a column for each attribute listed in the provided ERD diagram.
•Select primary key for each table as indicated in the provided ERD diagram.
•Identify foreign key relationship between tables as indicated in the provided ERD diagram.
•Enable referential integrity on the relationship.
•Enable cascade updates on the relationship.

STEP 4: Set Data Types for Table Fields
Back to Top
For every column in every table, update the data type as needed to enforce the domain constraints of the data.
•Dates should have a date data type.
•Surrogate keys should be auto-numbered.
•Numeric data should have a numeric data type.
•Character data should have a character data type.

STEP 5: Set Column Constraints
Back to Top
Set the following column constraints in your database.
•Student first and last name cannot be a null value.
•Course credit hours must be between one and four.
•Course name must be unique and cannot be a null value.
•Instructor first and last name cannot be a null value.
•Grade must be one of these values: A, B, C, D, F, I, W, or E. W signifies withdrawn and E signifies enrolled.

STEP 6: Add Data to Tables
Back to Top
Write INSERT statements to add at least 2–3 rows of data to each table in your database. Use any values that you like for each of the columns. Remember that you must add data to parent tables before adding data to child tables, because referential integrity is enabled.
STEP 7: Run the Script
Back to Top
Set the following column constraints in your database.
•Include a COMMIT command at the end of the script.
•Include SHOW TABLES command at the end of the script, to show all tables created.
•Include SELECT statements for each table at the end of the script, to show data inserted.
•Paste a copy of the output in a MS Word document named LastName_Lab3_Output.

Step 8: Save and Upload to Dropbox
Back to Top
When you are done, zip up the following files to the Week 5: iLab Dropbox:
•LastName_Lab3.sql script file.
•LastName_Lab3_Output Word document.

Rubric
Back to Top
Points will be awarded according to the following rubrics.
•5 points: Table created for each entity in the provided E-R model
•5 points: Column created for each attribute in the provided E-R model
•5 points: Primary key added for each table with unique constraints specified as column properties
•5 points: Data type set for each attribute
oDates should have a date data type.
oSurrogate keys should be autonumbered.
oNumeric data should have a numeric data type.
oCharacter data should have a character data type.
•10 Points: Relationships created as shown on the provided E-R model
oRelationships enabled for referential integrity
oRelationships enabled for cascade updates.
•10 Points: At least five rows of data added for each table
•10 Points: Column constraints added as indicated in project description, checked by adding rows to data with invalid values

oStudent name cannot be set to null.
oCourse credit hours are restricted to between one and four.
oCourse name must be unique and cannot be set to null.
oInstructor last name and first name cannot be set to null.
oGrade is restricted to be one of these values: A, B, C, D, F, I, W, or E (enrolled).