You are a Database Administrator working for a small software solutions firm. You have been assigned to help develop a beverage imports management system. High Spirits is a small importing company that specializes in wines imported from Australia, Chile, United States and United Kingdom. The owner, Tim Tipple, has been considering expanding his inventory to include beer, liquor and liqueurs. Due to the increased complexity in record keeping, Tim wants to improve the Shipping/Receiving and Sales management system. Currently, each department completes its own paperwork and maintains its own records with its own software application. Departments communicate details by telephone or paper. Several costly mistakes have resulted in the loss of too many good customers. To improve customer service and avoid communication errors, High Spirits owner wants one system that provides employees with access to all administrative functions. The new application will provide an integrated interface, so Shipping/Receiving can manage inventory levels, and Sales Managers can easily invoice customers and obtain customer account information. Mr. Tipple wants access to all features of the new application. Naturally, built-in security features prevent unauthorized individuals from obtaining sensitive information. Mr. Tipples long term plans include company expansion into new markets. He would like to open new branches in the future. You are part of a team of IT professionals hired to implement a business solution for High Spirits administrative problem. Your team understands the importance of integrating current business practices, rules and documentation into any new system.

General Requirements The High Spirits Imports Management System enables Shipping/Receiving and Sales Managers to effectively manage inventory and sales. The systems analyst on your team has produced a system chart that describes the proposed application based on interviews to discover Mr. Tipples requirements, company documents, and employee work habits and requirements. Figure 1: System flowchart for the High Spirits Imports Management System Sales Managers complete the initial paper-based sales contract, recording product particulars between the customer and High Spirits. They are responsible for inputting new customers and new sales into the system, and generating invoices. They maintain customer relationships, and deal with customer concerns or complaints. Shipper and receivers adjust inventory information, recording inventory particulars and quantities based on purchases and sales (transactions) of product. They are responsible for inputting new inventory into the system. Tim Tipple, the owner, can perform all functions including purchase new inventory.

Database Usage The systems analyst has discovered the following facts about how the database will be used: Since the way the database is described is fairly normalized, joins will be frequently used in the HighSpirits application. Typically, a sales manager will search for a customer by phone number. They will want to know the customers first and last name initially, and may opt to do a search for other information later on. Searches in the Products table typically involve a Product number, and any or all of name, country, quantity, price and type. Most often the search involves Product number, quantity and price. Searches in the Transaction table typically involve a Transaction number, type, and date. Searches in the TransactionDetails table typically involve the Product or Transaction ID, price and quantity. The Country, Size, Product Types and Transaction Type tables are searched for each new transaction. Product stock information tends to change often. New customers and transactions are added continuously throughout the year. Retail prices are at least 110% of cost. Discounts or higher retail prices apply at Mr. Tipples discretion. Unit cost price includes any duties or taxes. Cost is 91% or less of retail price. Payment Procedures Payments entered into the database incorrectly cannot be deleted. Instead, they are voided. A voided payment has a payment value of $0.00. A reason should always be given for a voided payment. By voiding a payment instead of deleting it, HighSpirits ensures that it has an accurate record of all payments made, even if some of the entries were originally incorrect. Also, voiding payments prevents employee theft. Auditing System In order to keep track of amendments to transactions, Mr. Tipple would like an auditing system implemented. The auditing system should record whenever changes have been made to the Transactions table. Specifically, you should record when the changes were made, what fields were affected, and what their old and new values were.

Based on the preliminary findings of the systems analyst, you will need to formalize the database design and use a DBMS (SQL Server, MySQL, etc) to build the database. You will NOT be required to build all the functionality as described above as part of this initial project. You will be responsible only for specific parts of the system and implementing specific features as described below. You should complete the following steps: 1. Analyze the data requirements described in the previous section. Decide which tables are required and which fields should go in which table. Normalize your design. If you wish, you may use an entity-relationship diagram. Create your table design showing the relationships between each table. It is now time for your instructor to check your progress. After you have finished the preliminary design for the High Spirits Imports Management System, contact your instructor for a brief review. 2. Using your DBMS, create an SQL script to create the High Spirits database. Name the database HSxxxxx, where xxxxx is your student number. Save your script as step2.sql. If you are using MySQL, save screen captures of the database creation steps and submit them instead. 3. Create the tables in the HighSpirits database. You do not need to specify relationships in this script. Save your script as step3.sql. 4. Create a default database diagram. Add primary keys and relationships where they make sense. Print your diagram. Create a script that will add the necessary primary keys and foreign keys to the appropriate tables. Save your script as step4.sql. 5. Create a script that will create the needed constraints to enforce the data rules Mr. Tipple has specified. Save your script as step5.sql. 6. Using the provided source documents (see pages 11-17 for customer invoices and purchase orders), populate your database with test data. Minimally, you need: 4 customers (include High Spirits as a customer so you can track purchase transactions). 5 transactions - at least 3 are sales type, 2 of which must be paid. 4 countries, types and sizes 6 products, each with a quantity specified Save your script as step6.sql 7. Create a script that will show a list of customers (first name, last name, and phone number) and the total number of sales transactions they have made. Save your script as step7.sql. After running the script, save a screen capture of the output and save it as step7-output.jpg 2020 Page | 9 8. Create a script that will show a list of products (product name, type, size) that have been purchased. Note: You must use an outer join for this query; a subquery is not acceptable. Save your script as step8.sql. After running the script, save a screen capture of the output and save it as step8-output.jpg 9. Create a script that will show a list of products (product name, type, size, supplier) that are from Australia. Save your script as step9.sql. After running the script, save a screen capture of the output and save it as step9-output.jpg 10. Create a script that will show a list of products (product name, type, size, customer, retail price, quantity sold). The script should also calculate the sum of the price field and the sum of the quantity sold from all times the products were sold and display it as a calculated field. Do not include purchases (Remember the status field is set to 0 for sales and 1 for purchases). Save your script as step10.sql. After running the script, save a screen capture of the output and save it as step10-output.jpg 11. Using your DBMS Help feature, explore the use of the SHOW command to display the contents of your database. Create a script that will display a list of tables in the database. Save this script as step11a.sql. Then create a script for each of the four main tables (Customers, Transactions, Products, Transaction details that will display all of the columns in the table. Save your scripts as step11b.sql to step11e.sql. 12. Finally, you will need to create the HS_Employees database. Using the data in the HS-Employees.xls spreadsheet, create a script to populate the Employees database with the data found there. Employee IDs should be unique and start with the two employee initials and then increment by a value of 1. It should be the primary key. Social Insurance numbers are unique for each individual. However, this does not make for a good Primary Key. You must ensure that there is not the ability to incorrectly enter someone elses SI number by mistake by making this field unique. Create the employee database and populate the employees table with the data as indicated above. Save your scripts as step12.sql and step12a.sql