Demonstrate how would you set up a relational database for the following data. Express your design completely, showing all the data fields and records in the proper places based on the data below. You will need to show all your tables filled with data from below. You will not have to provide record layouts for any of your tables. The data for your database is in the narrative below: A small online sales/retail company called Express Electronics sells accessory items for cell phones, tablets, and notebook computers. See the sample data below. Cody Bronco; 68 Cleveland Drive; phone: (318)356-6756; credit# 645234476; purchase no.'s 91254.1 - 91254.3; purchases: (1) Blue Cell Phone Cover - $34.95; (1) Touch Screen Clear Overlay - $24.95; and (1) Cell Phone Car Adapter - $45.00. Louise Forrester, 46 German Street; credit # 545334978; purchase no.'s 92368.1 - 92368.2; purchases: (1) Red Tablet Case; $55.95, (1) Cell Phone Car Adapter - $45.00. Chloe Packard; 796 Blackwell Cove; credit # 986445234; phone: (523)775-3445; purchase no. 93565.1; purchases: (1) Black Leather Notebook Case; $105.00. Louise Forrester, credit # 545334978; purchase no. 94250.1; purchases: (1) Touch Screen Clear Overlay; $34.95. Notes: The owner would like to use the customer credit number as a way of locating each customer in the system. Purchase numbers have a one-to-one relationship with products. In assessing the design, you consider each customer transaction (above) occurred on a different business day for each week in the month of January 2023. Arrange the data according to relational database concepts learned in class. a) Show the data in one table (file) with all your data records. a. Explain why this would not be a good way of organizing data on disk. b) Convert the unnormalized sales table (file) to a relational database design. Fill each database table in your design with data from the question such that no information is lost. Identify the data fields, primary key, foreign key, and compound keys. a. Describe why it is better to store data on disk in this way rather than all in one table. c) Create an Entity Relationship Diagram for the Database