Hello Johann,

Generally the answer for modeling this kind of data in a relational DB is to make it a long skinny table. Instead of a row per sample and a column per feature, or a row per feature and a column per sample, you could make it one row per sample/feature combination (2.3 million rows).

What was the internal server error you got?

Thanks,
Chet