22.05.2017 Views

BIS 445 DeVry All Week I Labs

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Note! Submit your assignment to the Dropbox located on the silver tab at the top of this page. (See the Syllabus section<br />

"Due Dates for Assignments & Exams" for due dates.)<br />

Remember This! Connect to the iLab here.<br />

iLAB OVERVIEW<br />

Scenario and Summary<br />

You will start with a comma delimited file that looks like this:<br />

When you are finished moving the data into the data warehouse, you will have split the customer, order, and product<br />

information into their own tables and, as a result, create a star schema that looks like this:<br />

As you can see, the FactOrders table has become a fact table containing statistics we might want to analyze as<br />

managers of a company. The fact table contains the primary keys of the other tables as foreign keys. Also in the fact<br />

table (FactOrders), we have stored the result of Price*Quantity in a newly created column called Sales_Total.<br />

Sales_Total is a fact we would like to analyze using an OLAP tool, such as a pivot table, in the future.<br />

The primary key of the FactOrders table is a Surrogate_Key which has been generated by the database management<br />

system.<br />

In the star schema, the products and customers table have become dimension tables. Furthermore, the star schema<br />

removes the duplicated customer and product names that existed in the original comma delimited file and puts them in<br />

normalized customer and product tables.<br />

Last of all, the star schema violates the third normal form, which says that no calculated fields should exist in the design<br />

(schema). In this case, the Sales_Total column is a calculated field.<br />

This violation isn't a problem because in a Decision Support System, software that accesses a data warehouse, it is<br />

acceptable to violate normal forms if it speeds up SQL queries by minimizing table joins and storing calculations in the<br />

database.<br />

Your task is to create a star schema that is capable of holding the information in the comma delimited file, and then<br />

load the star schema with the data from the text file. You will load the comma delimited data file into a temporary table<br />

in the SQL database. After you design the star schema, you will use SQL statements to populate the star schema with<br />

the necessary data from the temporary table. Finally, you will analyze the data by order year in order to find out which<br />

customers have the highest to lowest sales.<br />

Deliverables<br />

Submit the YourName_Lab2_Questions.docx to the <strong>Week</strong> 2 iLab Dropbox.<br />

<strong>BIS</strong> <strong>445</strong> <strong>DeVry</strong> <strong>Week</strong> 3 iLab<br />

Using Enterprise Data to Create Pivot Tables<br />

Note! Submit your assignment to the Dropbox located on the silver tab at the top of this page. (See the Syllabus section<br />

"Due Dates for Assignments & Exams" for due dates.)<br />

Remember This! Connect to the iLab here.<br />

iLAB OVERVIEW<br />

Scenario and Summary<br />

You are working as a data analyst for a large manufacturing firm. You have been asked to develop a series of pivot<br />

table queries, which will present aggregated views of corporate data that can be used for decision support and trend<br />

analysis by decision-makers.<br />

Using SQL, you can create aggregated views of your data. Pivot tables are especially useful if you are analyzing large<br />

volumes of data. For example, if you wanted to determine the average value of sales for each sales person in your<br />

database, you could use a pivot table to aggregate thousands or millions of sales records. This is much faster than<br />

attempting to scroll through all of the available records.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!