No. The issue is that you quickly have trillions of rows. You don't need a relational db setup or fancy non-relationary db solutions. Both are well known anti-p

No. The issue is that you quickly have trillions of rows. You don't need a relational db setup or fancy non-relationary db solutions. Both are well known anti-patterns. One row per sample falls over quickly for regularly sampled data. What does work for large regularly sampled datasets is array storage solutions like hdf, or image formats, etc etc. It's the same reason and same approach for your vacation photos. You wouldn't put each pixel in the db, but you might very well have a db with a row for each photo. Use a db for the non-regular portions (e.g. an index of datasets) and array storage for the actual data itself.