- Term Papers, Book Reports, Research Papers and College Essays

Kudler Fine Foods Database Analysis

Essay by   •  November 9, 2010  •  Case Study  •  1,742 Words (7 Pages)  •  2,295 Views

Essay Preview: Kudler Fine Foods Database Analysis

Report this essay
Page 1 of 7

Kudler Fine Foods Database Analysis

POS410 SQL for Business


Kudler Fines Foods is a rapidly growing small business located in Southern California. Founded in 1998, Kudler specializes in providing quality gourmet foods to a wide range of customers.

When Kudler opened its first store back in 1998, Microsoft Access was chosen as the database platform used to track inventory, orders and customers. While this initially proved to be an adequate solution, it has since outgrown its usefulness. Now with three stores and a fourth due to open soon, a new database management system must be put into place.

One of the most detrimental problems with the Microsoft Access database is that it is limited to a file size of only two gigabytes. While this may initially seem like a large files size, it can rapidly grow and eventually reach this maximum size in a relatively short amount of time. This one drawback alone is reason enough to pursue a better solution.

Another aspect of Microsoft Access that does not scale well is that it will not accommodate multiple users simultaneously. The database needs to be updated continuously by multiple users at each store. Running one instance of Microsoft SQL Server 2000 in a centralized location could easily handle the database needs of all of the store locations. Connections to the database could be made via Virtual Private Network (VPN) connections over the Internet. Updates to the database can be further streamlined by developing and utilizing a web based interface.

The best solution for Kudler Fine Foods would be to implement an enterprise level database solution. Microsoft SQL Server 2000 would be a great fit for the database needs of Kudler Fine Foods. Microsoft SQL Server 2000 will easily meet the current needs of Kudler Fine Foods and also meet their needs of the future as they continue their growth.

Existing Database Overview

Currently the Kudler database contains nine tables. Each table is designed

to support and facilitate the filling of orders placed by customers in the stores. Based upon the description of the tables that was posted on Kudler's intranet and our analysis, the tables may be described in the following manner:

The Customer table contains demographic data for each of Kudler's customers. The data in this table is used to access the name and address of customers for order processing and for special mailings for anniversaries and/or birth dates, etc. Each record in the customer table contains a customer_id field that is used to link the customer to the orders that they place.

The Inventory table contains the components that make up an Item. It is used for managing inventory and determining the availability of ingredients that go into prepared items, such as bakery products, etc. Each record in the inventory table is linked to the Item table by the item_id and to the Supplier's table by the supplier_id.

The Item table stores information pertaining to products that may appear on an order. It describes goods that can be purchased from a Store. The Item table is linked to the Inventory table by way of the item_id and to the Order Line table by the item_id field.

The Order table is used to record information pertinent to each order placed with a given store. Each order will have one or more entries in the Order Line table associated with it. The Order table is linked to the Order Line table by the store_code and the order_id. It also links to the Customer table via the customer_id field.

The Order Line table contains details on items appearing on an order. One or more order lines are associated with each order and each order line references an item being purchased with its description, quantity, price, etc. The Order Line table is linked with the Order table by the order_id and the store_code. It also links to the Item table by the item_id.

The Store table retains data for each store location, such as name, address, phone numbers, emergency contacts, etc. The Store table links with the Order table by the store_code.

The Supplier table contains data concerning wholesalers, vendors and other suppliers from whom inventory is procured. These goods are used to prepare saleable items or are simply resold in their acquired form. The Supplier table is linked with the Inventory table by way of the supplier_id.

The purpose of the Tax table is to provide tax rates applicable to orders placed at a given store. The Tax table is linked with the Order table by way of the store_code field.

The Tender table provides a means to record the methods of payment used for an order. For example, an order may be paid for partially by cash and partially by credit card. The Tender table is linked with the Order table by the store_code and the order_id.

Recommendations for Improvements and/or Enhancements

Based on the descriptions of the tables, it is recommended that the Kudler database undergo the following enhancements. The Tax table should only be linked to the Store table. The tax jurisdiction is based on the stores location and not on the order. The store_code should be removed from the Order Line table, since the table will function in the same manner it currently does without the store_code in it. Information regarding the store could be linked back to the store by joining the Order Line table with the Order table and then using the store_code in the Order table to match it with the Store table. The Tender table should also have the store_code field removed from it for the same reason given for the Order Line table. There should be an additional table added to track the sales personnel. Currently there is a field called sales_person_id in the Order table, but there is no table to link this information with.

An Overview of the SQL Business Application

The business application would be an online order processing system that would facilitate the orders from each of Kudler's locations, as well as an online ordering system for internet users to place orders without being in a store.

Key features

The key feature would be the integration of the stores ordering system and the online system. Each of these systems would store their data in the same database, which would allow for the tracking of both the customers orders by the store and orders placed online. This would facilitate the tracking of how an order changes based on where it is placed to determine if there is a



Download as:   txt (10.3 Kb)   pdf (129.7 Kb)   docx (12.9 Kb)  
Continue for 6 more pages »
Only available on
Citation Generator

(2010, 11). Kudler Fine Foods Database Analysis. Retrieved 11, 2010, from

"Kudler Fine Foods Database Analysis" 11 2010. 2010. 11 2010 <>.

"Kudler Fine Foods Database Analysis.", 11 2010. Web. 11 2010. <>.

"Kudler Fine Foods Database Analysis." 11, 2010. Accessed 11, 2010.