Jeremy Caney

During a discussion this weekend I realized that a lot of the complexity of DAL and ORM projects stems from the attempt to accomplish both needs in the same library. And perhaps that makes sense; it might be argued that the only pragmatic difference is cache strategy. Nonetheless, as with all development projects, identifying the project requirements and evaluating them against the innate benefits of each approach is critical.

I sat down to write a defense of stored procedures with specific regard to DAL/ORM solutions, but found myself painted into a corner. When it comes to generated code, many of the benefits of stored procedures start to crumble - or, at least, deny the luxury of automated approaches.