database - General Oracle Data Collection Storage -


I am preparing a new laboratory database. I want to store raw results together for all tests.

In some cases, the result is a single value. However, the result is sometimes a raw wave or signal.

The case below is the ideal (and why)? ... or provide your own ideal choice.

Option 1: Store each individual data as a separate result line (with offset from T = 0). Option 2: Create a signal_header table (start time, sample rate, units, etc.) that are linked to a raw_signal_value table (signal, offset index, value)

OR

OR

Option 3: Store raw data in an external file to recover it when necessary.

In addition, in the related post, I asked whether a normal result table is to be stacked in hair tables on the basis or not accurate and scale (data type).

I would like to avoid option 3 - if you are going to use to store raw results In a database, you can also use it to store all the results.

Option 1 sounds like you would duplicate a lot of data for each result line, and change only two values ​​(time offset and value).

Three options which you suggest, I go with Option 2. You will be able to store a singing result result line results for each result, and also the details of the results available in DB, without extending the result table itself

how you use the data and Based on how many statistics of the waveform you get per result, I would like the wave / signal to be a string (like the values ​​separated by a comma).


Comments

Popular posts from this blog

c++ - Linux and clipboard -

What is expire header and how to achive them in ASP.NET and PHP? -

sql server - How can I determine which of my SQL 2005 statistics are unused? -