Proposed Purpose for the Database

Huffman trucking utilizes this database to maintain and access important data about Huffman Trucking’s fleet vehicles such as vehicle and tire maintenance services, work orders, and unique vehicle identification information. Additional information that can be found in the database is vendor contact, parts inventory, and purchasing history. This database provides an efficient way to track and schedule routine maintenance, track parts inventory which helps prevent slowdowns in production.

Parts Inventory Purchases
Transaction ID Auto Number Primary Key
Purchase Date Date/Time
Purchase Price Currency
Quantity Numeric Value

Rationale of primary key –
The Transaction ID should be a unique number which can be tracked back to the parts inventory purchase table and will make a perfect Primary Key.

Rationale for foreign key 1 –
There will be no foreign keys in this table as no other table for the Fleet Truck Maintenance will be using one of the values as a Primary Key.

Rationale for foreign key 2 –
There will be no foreign keys in this table as no other table for the Fleet Truck Maintenance will be using one of the values as a Primary Key

Parts Inventory Issues
Transaction ID Auto Number Foreign Key 1
Issue Date Date/Time
Purchase Price Currency
Quantity Numeric Value
Parts Inventory ID Auto Number Primary Key

Rationale of primary key –
The parts inventory ID will be used as the primary key for the Parts inventory issues as it will be an auto number. The transaction ID can’t be used as it is already a Primary Key for another Table.

Rationale for foreign key 1 –
The Transaction ID will be Foreign Key 1 as it is being used as a Primary Key for the parts inventory table.

Rationale for foreign key 2 –
There will be no foreign key2 in this table as no other table for the Fleet Truck Maintenance