Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
AskSQLTeam
Ask SQLTeam Question
0 Posts |
 Posted - 2004-02-24 : 08:22:22
|
| Mark writes "Hi All,I am upgrading a project Management Database and there is a table called ProjectSatageDates which has the following fields; [int_ProjectStageDateID] [int] IDENTITY (1, 1) NOT NULL , [int_ProjectNo] [int] NOT NULL , [int_ProjectStageID] [int] NOT NULL , [int_DateTypeID] [int] NOT NULL , [sdtm_ProjectDate] [smalldatetime] NOT NULL Now the rules are that a project can have up to 4 stages and 6 data types.After analysing the above the best srtucture that I can think of is to have 2 tables as shown below;tbl_ProjectStageProjectStageID {PK}ProjectNo {FK links to tblProjects(not shown here)}StageID {look-up Value}tblProjectStageDateProjectStageDateID {PK}ProjectStageID {FK to tbl_ProjectStage}DateTypeID {look-up Value}DateCommentsCan I have your comments on the aboveBest Regards,Mark" |
|
|
|
|
|
Table Design in a Project Management App