I worked on a system a couple of years ago where we ran calculations nightly and then we write the results of this calculation to a row in a table for caching p

I worked on a system a couple of years ago where we ran calculations nightly and then we write the results of this calculation to a row in a table for caching purposes. This row was then fetched by another job to generate a PDF. We used SQL for this because Reporting Services could build a pdf from a row in a table. It's not a good solution. This type of data doesn't need to be searchable. It's using a database server as a caching mechanism. That seems wrong. Seems like memcached, mongo, couch, or anything else would have been better. Heck, people have been using memcached for a long time, and yet all of a sudden people don't see a use for NoSQL setups? Are we sure we're not just doing the same old "Defend what you know" dance?