ECET 450- WEEK 2 iLab and Practice exercise

ECET 450: Laboratory 2

Part A:

Purpose:

This exercise involves normalizing a small part of a DB.  The steps to complete this exercise include getting the data items into 1NF, 2NF, and 3NF.  The final step is to generate the ERD for the table or tables that are in the dependency diagram in 3NF.

Discussion:

Some small business wants to keep track of office furniture, computers, printers, etc.  A sample of the ITEM records is shown below:

1.     Draw the dependency diagram using the data in the table.  Make sure to label the transitive and partial dependencies.

o

2.     Using the dependency diagram developed in step 1, create a set of dependency diagrams that meet 3^rd Normal Form requirements.  Rename attributes to meet the naming conventions. 

Create new entities and attributes as necessary.

Part B:

Purpose:

This laboratory provides practice in the creation of realistic tables and their relationships using Oracle SQL*Plus and introduces writing SQL*Plus script files.  This laboratory exercise creates a relatively simple invoice system using SQL statements.  This DB schema is used throughout the next several weeks of laboratory exercises.  The final product is an SQL script that makes it possible to initially create and re-create, if need be, the DB schema in order to do to the later laboratory exercises.

Procedure:

Using your assigned user name, password, and host string, log in to Oracle SQL*Plus.  Record your dialog with a spool file.

Following the four requirements below, create the 5 tables shown later in this laboratory exercise, and enter all data as shown.  Be sure to record your interactions with SQL*Plus using the spool command.

1.      Use table names, attribute names, and data exactly as shown. The one exception is that you will omit the dollar sign and comma separators in the money amounts.  Accurately enter the data as you will need these tables in future laboratory assignments.

2.      Save all of your commands in a single script file for printing and submission. This file should each contain a minimum of your name and the date in comments at the beginning of the file, and any other comments you feel add to the understanding of the script file.  Copy and edit your spool file to create the load_tablesXXX.sql file where XXX are your initials.  The only items that should be in this load_tablesXXX.sql file are your comments and the SQL statements that drop tables, create tables, insert data values, and display table.  Be sure to remove all incorrect commands and the Oracle responses to the correct commands from the file.  Save this file for the future in case you have to rebuild these tables.  Be sure to include a printout of this file in your report.

3.      The second submission requirement is a printout of each of the 5 tables completely loaded with the specified data.  Use the SET LINESIZE command to avoid line wrap around of your table data.  Print your list file in landscape mode.

4.      All primary key and foreign key constraints should be named according to the method presented in the classroom.  If you have any questions about which attributes are primary and/or foreign keys, please ask about them.

5.      The ultimate test is the execution of this SQL script file in the following form:                       @ <path_name>/load_tablesXXX.sql

<First Page of tables>

REP Table

CUSTOMER Table

PRODUCT Table

INVOICE Table

LINE Table