I have a large amount of data from recordings (around 100Hz as well as 1Hz and less) and event data (time and event). I am wanting to know the best structure to use which will keep the size of the db down, enable easy searching of the data within the recordings (all records where the value is above X).

At the moment I'm thinking of a simple relational design:
Recording
-RecordingID
-Comments
-EventID
-SignalId

Event
-EventID
-Time
-Event
-Comment

Signal
-SignalID
-TimeSeriesID
-SignalValuesID

TimeSeries
-TimeSeriesID
-Values

SignalValues
-SignalValuesID
-Values

I'm not sure this is the best way - can anyone help please?

Thanks,
David

we're even less sure than you are, because you're familiar with what you're doing and we're not

maybe if you gave several sample rows from each table so we could understand your data?