Reputation: 3
I have an old database with 2 tables:
table1=standard items
table2=all items
This database was first design to be a tool for a single project.
I like to have one single database that handles all projects, but that require a new design - what is the best design when need the database to do this:
Need help on this: a. what is the best practice, when i need to copy items (sometime several of the same item) b. how do i seperate new items between PMs c. how do i get all items together in table2
I really need help on best practice on this one.
Upvotes: 0
Views: 132
Reputation: 91356
There is no need for two tables, you can indicate with flags and dates where an item is in terms of work. Consider the following sketch.
Project
ProjectID
Contact -- fk to PM id. This is just the lead, all other contacts are
in the PersonsProject tables
Etc
Items -- All
ID -- pk
ProjectID - fk to Project
AssignedTo - fk, but it all depend on whether a person is in charge of an item
Stage and / or status -- fk to list
Description
Notes
Created date
Completed date
Deleted date
Deleted reason
Created by
Deleted by
Persons
ID
Etc
PersonsItems or PersonsProject
PersonID
ProjectID
Notes
etc
Possibly a table of assigned items
PersonID
ProjectID
ItemID
In addition, if you have a limited list of possible items, you might need an Item list table, in which case the ItemListID would go into the Items table and Description would come out.
Upvotes: 1