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 |
|
Spiral
Starting Member
2 Posts |
 Posted - 2009-07-07 : 17:40:08
|
| Hey guys I could use some help.I have a situation where i have 1- 100 fields of data coming in on a timed basis. Average is 10 at a time.Should I do this:id|field|value|timestampwhich means each time I recieve data I get 1-100 records,or should I do this:id|field 1 |Field 2| ......|Timestampin which case I get 1 record but an average of 90 empty fields.any advice is appreciated. |
|
|
SwePeso
Patron Saint of Lost Yaks
30421 Posts |
Posted - 2009-07-07 : 17:49:30
|
First option.Keep your database as normalized as possible.
N 56°04'39.26"E 12°55'05.63" |
 |
|
|
Spiral
Starting Member
2 Posts |
Posted - 2009-07-08 : 14:12:22
|
| so a lot of small rows (4 fields) is better than a smaller amount of large rows (103 fields) that have a lot of empty fields?Just making sure everyone understands what I'm ending up with.Thanks again guys |
|
|
|
Skorch
Constraint Violating Yak Guru
300 Posts |
Posted - 2009-07-08 : 14:27:47
|
| In short, yes.Some days you're the dog, and some days you're the fire hydrant. |
|
|
|
SwePeso
Patron Saint of Lost Yaks
30421 Posts |
|
|
|
|
|
Best way to design database