485711 Building the Physical Model

Lab 3 of 7: Building the Physical Model Your assignment is due by Sunday, end of week, 11:59 p.m. (MT). Submit your assignment to the Dropbox located on the silver tab at the top of this page. For instructions on how to use the Dropbox, please click here. L A B O V E R V I E W Scenario/Summary Beginning with this lab, and continuing through the remaining weeks you will be doing all of your work in Oracle itself. The editor interface to the Oracle server is SQL*Plus, and by now you have received your logon id and password and should have at least made sure you can connect. If for any reason you have not done so, please do so now before continuing any further. If for any reason you cannot connect then you need to let the instructor know ASAP so that any problems can be resolved. Before attempting Lab #3, you need to be sure you have read through the SQL*Plus tutorial which can be found in Doc Sharing as well as under the SQL*Plus Tutorial tab in Week 3. This tutorial describes the functionality of the editor and will step you through the process of setting up and using the SQL*Plus in the iLab environment so that it will best serve your needs for the remainder of the labs required for this course. The lab for this week addresses taking a logical database design (data model) and now transforming that into a physical model (tables, constraints, and relationships). As part of the lab, you will need to download the ZIP file titled "Lab 3 Support Document" from Doc Sharing. This ZIP file contains three documents: Lab 3 Relationship [login to view URL], Lab 3 Meta Data [login to view URL], and Lab 3 Input Data.doc. Your job will be to take the meta data defined in the data dictionary spreadsheet document, and using the relationship diagram as a guide define the table structures and constraints using both CREATE TABLE and ALTER TABLE statements. Once this has been done, you will need to write the INSERT INTO TABLE statements to insert the data provided into the table. The data should verify that the constraints you have created are valid and define the correct referential and data integrity constraints asked for. Narrative/Case Study For this lab you be working with command-line SQL to build a series of relational of tables, using SQL CREATE statements in a script file format for the Student Database and then populate those tables through the use of INSERT statements with sample data. You will need to create a script file and name it [login to view URL] containing the following code: The drop table statements listed later in the specifications of this lab. The CREATE TABLE statements required to build the seven (7) tables. The INSERT statements necessary to insert all of the sample data. Seven select statements to verify that the data is in the tables and accessible. To help you accomplish this task successfully you are being supplied with the following three documents which can be found in the Doc Sharing tab on the course web site: A Relationship Diagram of the database showing in graphical form the 1-M relationships between the tables ([login to view URL]). A Meta Data chart providing information about table names, column names, etc. Be sure to follow this reference exactly when constructing your CREATE TABLE statements ([login to view URL]). A listing of sample data to use when writing the INSERT statements to populate the tables ([login to view URL]). The following guidelines are being provided to help assist you in creating your script file: Create the tables in the order shown in the data dictionary. Use the names for the tables and columns as listed in the Meta Data chart – DO NOT CHANGE THEM AS IT WILL AFFECT YOUR GRADE. Creating CONTRAINTS - Create all constraints as indicated in the data dictionary. Constraint prefixes must be as follows: Primary key constraint – PK Foreign key constraint – FK Check constraint - CC Explicitly name all constraints PRIMARY KEY, FOREIGN KEY, and CHECK constraints to reflect: ConstraintPrefix_TableName_ColumnName (For example, to name a PRIMARY KEY constraint on the SID column in the student table you would use PK_STUDENT_SID.) For this lab you do not have to explicitly name NOT NULL constraints Create all PRIMARY KEY and NOT NULL constraints within the CREATE TABLE statements at the column level (line level), unless the Primary Key is a combination Primary Key (yes, there is one). Combination Primary Key constraints must be created at the table level. Create all FOREIGN KEY and CHECK constraints at the table level using ALTER TABLE statements. All constraints must be added prior to populating the tables with data. Create all of the tables and all of the constraints before populating any of the tables with data. Insert statements must be in the same order as the tables are created (follow the order in the sample data file). ALL character strings must be enclosed in single quotes. This includes alpha strings and alphanumeric (remember that any formatting within a numeric strings makes it alphanumberic). If you are inserting a NULL, do not enclose the word NULL in single quotes, as this will insert the word NULL into the row. To insert a null you simply use the word NULL. Deliverables The deliverable for this lab will include the following documents. Your script file. Make sure your name is in a comment area at the top of the script file. Your lab output file created using a spool session in SQL*Plus. Be sure to use the SET ECHO ON session command when creating the output files so that both the SQL commands and results will show in the output. Be sure your name is on all documents and that all documents have been included in a single ZIP file for this weeks assignments. L A B S T E P S STEP 1: The DROP statements The following DROP TABLE statements must appear at the top of your script file. This will allow you to run and re-run your script file as often as you need to. The first time you run your script file you will get an ERROR on the drop statements say the Table or View does not exist. This is true since it has not been created yet, but the error is more informational than anything. After the first time you will not get this error again. DROP TABLE ENROLLMENT CASCADE CONSTRAINTS PURGE; DROP TABLE COURSE_SECTION CASCADE CONSTRAINTS PURGE; DROP TABLE COURSE CASCADE CONSTRAINTS PURGE; DROP TABLE TERM CASCADE CONSTRAINTS PURGE; DROP TABLE STUDENT CASCADE CONSTRAINTS PURGE; DROP TABLE FACULTY CASCADE CONSTRAINTS PURGE; DROP TABLE LOCATION CASCADE CONSTRAINTS PURGE; STEP 2: The CREATE TABLE statements Next, define the CREATE TABLE statements for the seven tables that you are to create based upon the ERD and Data Dictionary that you have been given for this lab. Be sure to follow the guidelines given above on how and where to create the different types of constraints for each table. STEP 3: The INSERT statements for the data The final step of the lab will be to create the insert statements to insert the sample data into the tables created in Step 2. You might find it helpful to take the word document containing the sample data and save it as a text file. After doing this you could create the insert statements around the actual data that is in that file. The process for doing this should have been cover in one of the lectures for this unit. If it was not then ask your instructor to discuss this process with the class. STEP 4: Testing and verifying your script Now we come to the point of verifying that your script file works by creating all of the tables and inserting all of the data. To verify this you will need to create a output file and capture the results being returned to the session by using the spool COMMAND outlined in the tutorial "Using Oracle SQL*Plus". This output file will be one of the files you will be turning in for grading. This is the end of lab #3