I am currently migrating our currently test data that is stored in excel files to a database. Because the type of data in the test results are going to grow we decided to go with nosql instead of sql.

I was planning on using a document database to store the data in but realized I'm not entirely sure how to store the data for it to be efficiently read.

The idea is that you have unique keys that help you find the data you are looking for quicker.

The data columns in the excel are:

  • Date
  • Model of device
  • Version of software
  • Type of test
  • A bunch of other columns that include the test data (% of something, Count of something, etc...)

So these are the columns and there are multiple rows of his kind of data.

Would a nested document be used here?

i.e. [Type of test] -> [Date] -> [Model of device] -> [Version of software] -> [Bunch of test data]

Am I even using the right database type?

  • Are test data updated only when creating/updating a test?
    – dzieciou
    Commented May 4, 2019 at 9:51

1 Answer 1


Not clear what "[Bunch of test data]" looks like so this is hard to answer. I'd likely have each document include the other items you mention as keys and index those fields so you can query against them quickly.

If "Bunch of test data" is JSON, you could achieve similar results using a modern DB that supports JSON (e.g. Postgres or SQL Server)

Whether you shuld use SQL or NoSQL is a much bigger question.

  • I updated my document a bit more to make it more clear. Are you saying you would create a document for each data entry? Because the test results contains say 100 rows of the column I mentioned, using that method would generate 100 documents. Is there a way to consolidate the data into one document?
    – tyleax
    Commented Dec 4, 2018 at 22:38
  • I was suggesting a document for each row in your spreadsheet. But, if you have fixed columns in every row, then NoSQL doesn't feel like a good fit, unless there are other reasons you want to leverage a document store?
    – ernie
    Commented Dec 5, 2018 at 19:29
  • The fixed columns are not really fixed. I suspect over time as requirements come in there will be more columns and some will disable. I'm worried if I use sql that a table will not be normalized anymore and will have lots of null entries.
    – tyleax
    Commented Dec 5, 2018 at 22:32

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.