Storing timeseries data with dynamic number of columns and rows to a suitable database
Usually a dynamic data problem like this can be solved by storing the dynamic portion of the schema in its own table, transposed as rows.
For example you can have an Intervals table where one column is called Interval and another column called Values. Interval would store 100, 200, 300 etc for each instance of values for that interval.
You could either store the Timestamp as a column in this table too, or my recommendation would be to normalize Timestamp into its own table with a TimestampId that is a foreign key field in your Intervals table.
Implementing your schema this way then allows you to not worry about how many dynamic Intervals are created since this it's a row based generic solution.