Placeholder

MIS 582 DeVry iLab 3 Latest

$30.00

Quantity:

Product Description

MIS 582 DeVry iLab 3 Latest

MIS 582 DeVry iLab 3 Latest

MIS582

 

MIS 582 DeVry iLab 3 Latest

iLab 3 of 4: Database Construction Using MySQL (100 points)

Note! Submit your assignment to the Dropbox, located at the top of this page.

(See the Syllabus section “Due Dates for Assignments & Exams” for due dates.)

iLAB OVERVIEW

Scenario/Summary

In this assignment, you will learn to create a Database Schema from a given ERD. To complete this assignment, you will need to be able to run MySQL via Omnymbus.

Using the documentation listed at the bottom of this tutorial, please ensure that you can connect to MySQL/Omnymbus via the account your Professor has e-mailed to you, that you can properly name a database, and that you can run an sql script under that database. Please consult with the document titled MySQLOmnymbusSupport.docx located in the Doc Sharing folder titled Omnymbus Tutorial Files for instructions on how to get help for any issues that you are having with the MySQL/Omnymbus Environment.

Deliverables

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

Review the ERD below to understand the entities, attributes, primary keys, and relationships that you will create in your MySQL database.

STEP 1: Create a New Database

Just like you did in the Week 1 iLab, create a new database following the naming conventions we are to use for our databases, as specified in the tutorial file Creating a Database within MySQL.pdf listed in the doc-sharing folder titled “Omnymbus Tutorial Files” in Doc-Sharing. All of our work in this iLab, will be done under this database.

STEP 2: Open MySQL via Omnymbus, Create SQL File, Drop Table

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.

But first include the following commands at the top of your script:

SET FOREIGN_KEY_CHECKS=0;

DROP TABLE IF EXISTS STUDENT;

DROP TABLE IF EXISTS CAMPUS;

DROP TABLE IF EXISTS ROOM;

DROP TABLE IF EXISTS COURSE;

DROP TABLE IF EXISTS INSTRUCTOR;

DROP TABLE IF EXISTS APPROVED_INSTRUCTOR;

DROP TABLE IF EXISTS CLASS;

DROP TABLE IF EXISTS STUDENT_GRADE;

SET FOREIGN_KEY_CHECKS=1;

STEP 3: Add Tables, Set Primary Keys and Foreign Keys

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

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

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

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

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.

Give your script a run, by uploading into Omnymbus and executing it just like you did in iLab1.

Paste a copy of the output in a MS Word document named LastName_Lab3_Output.

Step 8: Save and Upload to Dropbox

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

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.

10 Points: Relationships created as shown on the provided E-R model

Relationships enabled for referential integrity

Relationships 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

Student name cannot be set to null.

Course credit hours are restricted to between one and four.

Course name must be unique and cannot be set to null.

Instructor last name and first name cannot be set to null.

Grade is restricted to be one of these values: A, B, C, D, F, I, W, or E (enrolled).