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 |
|
dblk22vball
Starting Member
1 Post |
 Posted - 2009-10-09 : 11:41:34
|
| I am working on a project where data will be stored for a test on our manufacturing floor.The data to be saved for each UUT (unit under test) will be: Fixture #, Employee #, Serial #, Timestamp, Test Result, Data.The problem I am having is that the data portion will be variable in length (acquiring data from 7 sensors, for X amount of time, which means probably 100s of data points for each UUT).Most of the examples that I have come across go like this:Name Address CityWhich is great, if your data is a constant number of fields, but mine will be changing.So how do I save all of the data per each device??I was thinking that I could save the Fixture #, Employee #, Serial #, Timestamp, Test Result, and the 7 data points from each test, but that seemed silly to write the Fixture #, Employee #, Serial #, Timestamp, Test Result for each sample during the test. |
|
|
webfred
Master Smack Fu Yak Hacker
8781 Posts |
Posted - 2009-10-09 : 11:51:13
|
1 UUT can have many sensor-data?Your UUT_Table needs a PrimaryKey (identity column)Then create a table SensorData with a column corresponding to that PK.It is the same like Order and OrderDeatail and so on...
No, you're never too old to Yak'n'Roll if you're too young to die. |
 |
|
|
|
|
|
|
|
Help with Database Structure