W
Weste
I am building an asset tracking database and have a design question. An
asset can be owned by either an employee, store, or a division. I have a
table for employees, stores, and divisions. Each table with some of its
fields is below. My question is about the Assets table. I need to track the
owner of the asset in the Assets table. Should I have 3 separate fields in
the table to indicate owner – EmployeeID, StoreID, or DivisionID where only 1
of the 3 can be populated for an asset? This doesn’t seem to be the best
solution for a normalized design. However, I am stumped as how to improve it
since the owners are so different. Any help would be greatly appreciated.
Assets Table
AssetID
AssetDescription
EmployeeID
StoreID
DivisionID
Employees Table
EmployeeID
LastName
FirstName
DepartmentID
JobTitleID
TerminationDate
Stores Table
StoreID
StoreNumber
StoreName
DeparmentID
Divisions Table
DivisionID
DivisionName
DepartmentID
Departments Table
DepartmentID
DepartmentNumber
DepartmentName
asset can be owned by either an employee, store, or a division. I have a
table for employees, stores, and divisions. Each table with some of its
fields is below. My question is about the Assets table. I need to track the
owner of the asset in the Assets table. Should I have 3 separate fields in
the table to indicate owner – EmployeeID, StoreID, or DivisionID where only 1
of the 3 can be populated for an asset? This doesn’t seem to be the best
solution for a normalized design. However, I am stumped as how to improve it
since the owners are so different. Any help would be greatly appreciated.
Assets Table
AssetID
AssetDescription
EmployeeID
StoreID
DivisionID
Employees Table
EmployeeID
LastName
FirstName
DepartmentID
JobTitleID
TerminationDate
Stores Table
StoreID
StoreNumber
StoreName
DeparmentID
Divisions Table
DivisionID
DivisionName
DepartmentID
Departments Table
DepartmentID
DepartmentNumber
DepartmentName