I only have experience with Java ORMs, so I'd say you forgot to add that ORMs require entity objects which basically duplicate everything - table structures, re

I only have experience with Java ORMs, so I'd say you forgot to add that ORMs require entity objects which basically duplicate everything - table structures, relationships, the whole lot is redefined. In my experience Java domain code written with an ORM is about 4x the LOC compared to using stored procedures to do the same job. Oh - and that 4x LOC gets you about 1/4 the performance, loosely speaking. I am a substantially more productive developer since I kicked all those abstractions to the kerb. It is the database and its structure that is the important part of an application. Building an additional layer of abstraction on top of an already existing abstraction no longer makes sense to me.