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 |
|
Looper
Yak Posting Veteran
68 Posts |
 Posted - 2010-01-06 : 08:08:28
|
| I am wanting to create a table that will store the following employee info:Standard1, SDate1, EDate1, Standard2, SDate2, EDate2, Standard3, SDate3, EDate3, Standard4, SDate4, EDate4, Standard5, SDate5, EDate5, Standard6, SDate6, EDate6Should I just add all the fields into one row like above with the employeeid or should I be trying to be smartere.g EmployeeId,Standard, SDate, EDate, StandardNo (which would be between 1-6)Basically what I want to know is the best way to store all these fields. |
|
|
khtan
In (Som, Ni, Yak)
17689 Posts |
Posted - 2010-01-06 : 08:19:50
|
the normalize way (the 2nd design you describe)
KH[spoiler]Time is always against us[/spoiler] |
 |
|
|
webfred
Master Smack Fu Yak Hacker
8781 Posts |
Posted - 2010-01-06 : 08:21:08
|
I would always take the second way you have shown.
No, you're never too old to Yak'n'Roll if you're too young to die. |
|
|
|
webfred
Master Smack Fu Yak Hacker
8781 Posts |
Posted - 2010-01-06 : 08:21:57
|
 sniped by KH 
No, you're never too old to Yak'n'Roll if you're too young to die. |
|
|
|
|
|
|
|
|
Table Design