wk 7 assign 6

The Strayer Oracle Server may be used to test and compile the SQL Queries developed for this assignment. Your instructor will provide you with login credentials to a Strayer University maintained Oracle server.
Imagine that you work for a finance industry-based organization. Your organization is looking to submit its database design documentation to an evaluation team in order to meet Sarbanes-Oxley (SOX) compliance. You have been assigned to assist in preparing the documentation of the organization’s sales database. You are asked to propose a data dictionary that can be used to document the following:

Employee (EmpNumber, EmpFirstName, EmpLastName, CommissionRate, YrlySalary, DepartmentID, JobID)
Invoice (InvNumber, InvDate, EmpNumber,  InvAmount, CustomerID)
InvoiceLine (InvLineNumber, InvNumber,  ProductNumber, Quantity)
Product (ProductNumber, ProductDescription, ProductCost)
Department (DepartmentID, DepartmentDescription)
Job (JobID, JobDescription)
Customer (CustomerID, CustomerName, CustomerAddress, CustomerPhone)

Write a three to four (3-4) page paper in which you:

Create a data dictionary that includes the following:

A description of the content for each field
The data type of each field
The format the data will be stored as in the field
The range of value for the field
A label, as required, if the attribute is a primary key or foreign key

Note: An example is shown in Table 7.3 in chapter 7 of the textbook.

Imagine that you are asked to identify the number of days that exist between the first invoice and last invoice for each month and complete the following:

Construct a query that will show the number of days that exist between the first invoice and last invoice, for each month, for each employee, using the DATEDIFF function. Be sure to provide the SQL script that will carry out this function.
Construct a query to show the expected payment date if invoices are due within 30 days of transaction.  
Construct a query that will show distinct area codes of the customers.

Create a plan of the necessary activities that would be required to implement a valid database design process by including the following:

Steps in the conceptual design stage
Steps in DBMS selection stage
Steps in logical design stage
Steps in physical design stage
Task details of each activity within each stage

Your assignment must follow these formatting requirements:

Be typed, double spaced, using Times New Roman font (size 12), with one-inch margins on all sides; citations and references must follow APA or school-specific format. Check with your professor for any additional instructions.
Include a cover page containing the title of the assignment, the student’s name, the professor’s name, the course title, and the date. The cover page and the reference page are not included in the required assignment page length.

Points: 120
Assignment 6: SQL Concepts and Database Design
Criteria
Unacceptable
Below 70% F
Fair
70-79% C
Proficient
80-89% B
Exemplary
90-100% A
1. Create a data dictionary.
1a. Include a description of the content for each field.
Weight: 5%
Did not submit or incompletely included a description of the content for each field.
Partially included a description of the content for each field.
Satisfactorily included a description of the content for each field.
Thoroughly included a description of the content for each field.
1b. Include the data type of each field.
Weight: 5%
Did not submit or incompletely included the data type of each field.
Partially included the data type of each field.
Satisfactorily included the data type of each field.
Thoroughly included the data type of each field.
1c. Include the format the data will be stored as in the field.
Weight: 5%
Did not submit or incompletely included the format the data will be stored as in the field.
Partially included the format the data will be stored as in the field.
Satisfactorily included the format the data will be stored as in the field.
Thoroughly included the format the data will be stored as in the field.
1d. Include the range of value for the field.
Weight: 5%
Did not submit or incompletely included the range of value for the field.
Partially included the range of value for the field.
Satisfactorily included the range of value for the field.
Thoroughly included the range of value for the field.
1e. Include a label, as required, if the attribute is a primary key or foreign key.
Weight: 5%
Did not submit or incompletely included a label, as required, if the attribute is a primary key or foreign key.
Partially included a label, as required, if the attribute is a primary key or foreign key.
Satisfactorily included a label, as required, if the attribute is a primary key or foreign key.
Thoroughly included a label, as required, if the attribute is a primary key or foreign key.
2a. Construct a query that will show the number of days that exist between the first invoice and last invoice, for each month, for each employee, using the DATEDIFF function. Be sure to provide the SQL script that will carry out this function.
Weight: 15%
Did not submit or incompletely constructed a query that will show the number of days that exist between the first invoice and last invoice, for each month, for each employee, using the DATEDIFF function. Did not submit or incompletely provided the SQL script that will carry out this function.
Partially constructed a query that will show the number of days that exist between the first invoice and last invoice, for each month, for each employee, using the DATEDIFF function. Partially provided the SQL script that will carry out this function.
Satisfactorily constructed a query that will show the number of days that exist between the first invoice and last invoice, for each month, for each employee, using the DATEDIFF function. Satisfactorily provided the SQL script that will carry out this function.
Thoroughly constructed a query that will show the number of days that exist between the first invoice and last invoice, for each month, for each employee, using the DATEDIFF function. Thoroughly provided the SQL script that will carry out this function.
2b. Construct a query to show the expected payment date if invoices are due within 30 days of transaction. 
Weight: 15%
Did not submit or incompletely constructed a query to show the expected payment date if invoices are due within 30 days of transaction.  
Partially constructed a query to show the expected payment date if invoices are due within 30 days of transaction.  
Satisfactorily constructed a query to show the expected payment date if invoices are due within 30 days of transaction.  
Thoroughly constructed a query to show the expected payment date if invoices are due within 30 days of transaction.  
2c. Construct a query that will show distinct area codes of the customers.
Weight: 10%
Did not submit or incompletely constructed a query that will show distinct area codes of the customers.
Partially constructed a query that will show distinct area codes of the customers.
Satisfactorily constructed a query that will show distinct area codes of the customers.
Thoroughly constructed a query that will show distinct area codes of the customers.
3. Create a plan of the necessary activities that would be required to implement a valid database design process.
3a. Include steps in the conceptual design stage.
Weight: 5%
Did not submit or incompletely included steps in the conceptual design stage.
Partially included steps in the conceptual design stage.
Satisfactorily included steps in the conceptual design stage.
Thoroughly included steps in the conceptual design stage.
3b. Include steps in DBMS selection stage.
Weight: 5%
Did not submit or incompletely included steps in DBMS selection stage.
Partially included steps in DBMS selection stage.
Satisfactorily included steps in DBMS selection stage.
Thoroughly included steps in DBMS selection stage.
3c. Include steps in logical design stage.
Weight: 5%
Did not submit or incompletely included steps in logical design stage.
Partially included steps in logical design stage.
Satisfactorily included steps in logical design stage.
Thoroughly included steps in logical design stage.
3d. Include steps in physical design stage.
Weight: 5%
Did not submit or incompletely included steps in physical design stage.
Partially included steps in physical design stage.
Satisfactorily included steps in physical design stage.
Thoroughly included steps in physical design stage.
3e. Include task details of each activity within each stage.
Weight: 5%
Did not submit or incompletely included task details of each activity within each stage.
Partially included task details of each activity within each stage.
Satisfactorily included task details of each activity within each stage.
Thoroughly included task details of each activity within each stage.
4. Clarity, writing mechanics, and formatting requirements
Weight: 10%
More than 6 errors present
5-6 errors present
3-4 errors present
0-2 errors present