• As a developer having finished a couple of large projects using an ORM (Entity Framework) I can tell you that they add more than they take away. Most DBAs take issue with ORM frameworks because they feel they are giving their baby up for adaption. But if you consider that some frameworks such as Entity Framework still allow you to use CRUD stored procedures, Views and Transactions then there is not that much to be worried about.

    Yes you do loose some finite control but it rarely a large issue. Yes in a very high performance scenario were sub seconds are important then I would second guess the use of an ORM and would really test the performance hit of using one before deciding on its implementation. But where the requirements for the application contains a lot of complex business rules and ongoing maintenance is likely to be a significant cost then an ORM definitely makes sense.

    Using an ORM simply put increases productivity. Therefore gentlemen I would just get used to it. These frameworks are here to stay and it is best that you educate yourself about the various frameworks so that you can make a positive contribution to the discussion rather than being a roadblock to productivity.