How to store, in an effective way, analyzer data into a relational database?

[knipph]

We want to store the "sweep traces" of a network analyzer in a relational database in a way that it saves as much as possible space without loosing resolution.
The solutions were we thinking on are to separate the x-axes information from the y-axes information and store it in different tables of the database.
Because the repeating character of the measurements the data in the x-axes will be nearly all ways the same. So we want to store only new data in the x-axes table as a different x-axes is detected.
In a third table we want to save the relation between the x and y data and other data that belongs to the measurement.
Question is are there other or better possibilities to solve this proble
m?

[Ben]

I know enough about DB design to know that I am not the best resource to answer this question.

I'm thinking based on your observation that the x-data quite freq the same. Cound you add additional field to the Y-data table that ID's the sample rate, start time, and sample count?This may eliminate the need forthe x-table and the X-reference.

Otherwise I think if you add a unique key filed to your x-table, you could bind to an equivelent filed in the y-table, thereby tossing the X-reference.

Just thinking,

Ben

[Ben]

Another thought,

Have you looked at DSC?

Ben

[knipph]

Hi Ben,
Thanks for you help.
The use of a third table that links the X-axe and y-axe table together depends on if I store the datapoints in the y-axe table sequential, so I need an identification of the points belonging together and I can have a varying number of data-points, (i.e. 401 of 801 ...) or I save it in one record.
The problem here is I have to save a varying nummer of points in tables with a lot of "datapoint columns".
Another solution is save the datapoints as a semicolon (;) separated text string in one field.
Problem now is the limitation in the max. text field length.
In my Oracle Rdb database I can use "Varchar" fields.
(is here no limitation??)
In other databases a "Note field" will maybe give a solution.
The question sti
ll is: What is the best solution and uses the smallest amount of space?
In the next week I will do some tests with the solutions mentioned.
Please let me know what DSC is??
Greetings Huub

[Ben]

DSC=Data-Logging and Supervisory Control.

It is an add-on for LV.

It include a Real-Time DB (i.e. optimized for what you are trying to do). THe DB is called Citadel and support SQL.

Ben