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.

 All Forums
 General SQL Server Forums
 Database Design and Application Architecture
 Best Database Design for Handling Dates

Author  Topic 

PicardsShineyHead
Starting Member

4 Posts

Posted - 2009-11-10 : 10:25:05
All-

I'm building a database that tracks issues that will be turned into small design projects... Right now the list is the ugliest Excel spreadsheet you could imagine (most of you have probably seen worse!)

  • Each record will have the same standard 12 dates for a pre-implementation plan
  • There will be a need to export this to Excel from time to time for scenario planning
  • They want to have for each of the 12 dates: Planned date, ECD if needed, and completion date


So my question is:
[1] Would would it be better to have a table with 36 field (12 dates x 3 view of the data)?
[2] Would it be better to have 3 columns for dates and 2 columns for date type and foreign key?


Thanks all!

SwePeso
Patron Saint of Lost Yaks

30421 Posts

Posted - 2009-11-10 : 10:26:33
I'd go for option #2, normalization.



N 56°04'39.26"
E 12°55'05.63"
Go to Top of Page

PicardsShineyHead
Starting Member

4 Posts

Posted - 2009-11-10 : 10:31:31
Thanks Peso, that's what I was thinking... But then it struck me that almost every example of a project management DB has [Task] [Start Date] [End Date].... So I didn't know if it was an expanded version of that...

-PG
Go to Top of Page

dportas
Yak Posting Veteran

53 Posts

Posted - 2009-11-10 : 15:02:06
I'd probably use columns for Planned, Estimated and Completed dates (I don't know what your "date type" column would be for).

On second thoughts, I wouldn't bother. I'd just use some standard PM software and get on with something more important...

Go to Top of Page

PicardsShineyHead
Starting Member

4 Posts

Posted - 2009-11-11 : 02:52:05
quote:
Originally posted by dportas

I'd probably use columns for Planned, Estimated and Completed dates (I don't know what your "date type" column would be for).

On second thoughts, I wouldn't bother. I'd just use some standard PM software and get on with something more important...





Thanks for that? Per my original post: I'm building a database that tracks engineering issues...

Go to Top of Page

dportas
Yak Posting Veteran

53 Posts

Posted - 2009-11-11 : 08:56:44
quote:
Originally posted by PicardsShineyHead


Thanks for that? Per my original post: I'm building a database that tracks engineering issues...



I'd just use some standard incident management software and get on with something more important...
Go to Top of Page
   

- Advertisement -