DRIVE | PROJECT PHONE SHOP PHONE SHOP PROJECT Full project file can be accessed at : 3 OVERVIEW Project Phone Shop is the assessment project that given in the course data warehouse from university. Phone Shop is a shop that operates around the world which based in Jakarta, Indonesia. Phone Shop is internationally-acclaimed shop because of their competitive pricing and service. To improve the customer’s experience and the efficiency of transactions, Phone Shop needs a database system that can analyze the operational data for decision making. Therefore, as Phone Shop’s database administrator are asked to implement data warehousing in the company using Microsoft SQL Server 2016. Report for phone purchases from suppliers, i.e. average expense and number of phone purchased. The average expense is acquired from average of multiplication between phone buying price and quantity of phones purchased. Report for services, i.e. total service earnings and number of services done. Report for phone sales to customers, i.e. total earnings from sales and number of phones sold. The total earning is acquired from total of multiplication between phone selling price and quantity of phones sold. Report for reviews, i.e. average score and minimum score of the reviews. Phone Shop’s CEO wants to see the report daily, monthly, quarterly, and annually. Furthermore, the CEO wants an ad-hoc report, which can be generated anytime as well. The report must be able to be viewed in terms of supplier, employee, branch, phone, service type, and customer REPORT REQUIREMENTS For supplier dimension requested as follows For employee dimension requested as follows For branch dimension requested as follows For phone dimension requested as follows For service type dimension requested as follows For customer dimension requested as follows - CEO needs data to make decisions about making purchases from the closest suppliers based on the city and address. - CEO needs data to make decisions about employee allocation based on the gender and where they live. - CEO needs data to make decisions about when the employee should retire based on the age. - CEO needs data to make decisions about whether the employee should get a pay raise based on the salary. - CEO needs data to make decisions where to build new branches based on the city and address of the available branches. - CEO needs data to analyze which phone makes the most profit based on its buying and selling prices. - CEO needs data to analyze the phones based on the brand. - CEO needs data to analyze how much stock a phone has from time to time. - CEO needs data to make decisions whether to raise or lower the price of the services. - CEO needs data to analyze the demography of the customers based on the gender and where they live. DIMENSION REQUIREMENTS The purchase report must be able to be viewed in terms of supplier, branch, employee, and phone. The service report must be able to be viewed in terms of service type, employee, and customer. The sales report must be able to be viewed in terms of employee, customer, branch, and phone. The review report must be able to be viewed in terms of phone and customer. All master tables, e.g. country, employee, customer, branch, and goods type must have at least 1,000 data and some of the master table are adjusted with the given data below. All header transactions must have at least 10,000 data, meanwhile detail transactions are 25,000. Employee and customer gender have Male or Female as its value with a varchar data type of transaction data. Convert the Male to "M" and Female to "F" in OLAP database. Customer and employee addresses can be updated, and old data don’t have to be stored. Phone buying price, phone selling price, service type price, and employee salary can be updated, but old data must be kept. NOTES FOR OLAP AND OLTP ANALYSIS MEASURE, DIMENSION AND FACT WHAT WILL DO? CREATE OLTP DATABASE AND GENERATE DATA CREATE OLAP DATABASE ETL PROCESS MULTIDIMENSIONAL DATA CUBE PIVOT TABLE Determine the measure and the aggregate function that is used for the measure according to the requirement! Determine the dimension and the fact! Determine the attribute or field for each dimension and fact table! In this step, do the analysis by using notepad or textpad : 1. 2. 3. The analysis can be looked in the link full project ANALYSIS MEASURE, DIMENSION AND FACT CREATE OLTP DATABASE AND GENERATE THE DATA In this step, create OLTP database according to OLTP design table that given before CREATE OLTP DATABASE AND GENERATE THE DATA CREATE OLTP DATABASE AND GENERATE THE DATA Generate dummy data using website https://www.mockaroo.com, with the format SQL CREATE OLTP DATABASE AND GENERATE THE DATA Generate dummy data using website https://www.mockaroo.com, with the format SQL CREATE OLTP DATABASE AND GENERATE THE DATA After generating the data, insert data into the table CREATE OLTP DATABASE AND GENERATE THE DATA After generating the data, insert data into the table CREATE OLTP DATABASE AND GENERATE THE DATA Other table creation processes are repetitive. For the whole query, see the link for the full project, in the OLTP Query file and the Insert Into folder CREATE OLTP DATABASE AND GENERATE THE DATA FilterTimeStamp table was created to accommodate the last time data was retrieved CREATE OLAP DATABASE CREATE OLAP DATABASE Full query can be looked at the link full project in the file OLAP Query Before jump into ETL Process, we need to create query for ETL Process ETL PROCESS As request in the requirements, CEO wants to see the report daily, monthly, quarterly, and annually. So it needs to create this query for viewing the data in the perspective time. ETL PROCESS ETL PROCESS