Not an April Fool’s post
Today I plan on writing a stored procedure. Not because I’m being forced to, but because the problem, as far as I can determine, requires a set-based solution. It’s a once-a-month process, doing bulk import, update and export of up to a million records, and it all needs to be completed within an hour or so.
There are some problems that simply work better using a set-based approach. As long as I have tests around the process, I don’t really have a problem creating a solution in SQL. I could try to use some of NHibernate’s DML capabilities, but frankly, they aren’t close to touching SQL’s featureset.
I think I’ve too often ditched previous approaches to how I’ve done software development in search of the One True Way, instead of evaluating when certain approaches work well, where they don’t, and choosing the best fit for the problem space.