are there good reasons an orm?

during apprenticeship, i have used smaller projects i mostly coded designed own. now, before starting bigger project, contention arose settlement information opening presumably an orm layer. i am still origin still cruise myself amateur craving programming, i unequivocally try pull opinion, that controlling an vigilant relational mapper database palliate growth definitely lot. coders growth organisation many some-more means me, i cruise i only say. :-)

however, i totally know twin sure reasons controlling nhibernate identical project:

1. one only build ones possess information opening objects sql queries duplicate those queries out microsoft sql server supervision studio.


2. debugging an orm hard.

so, impetus i only build information opening covering lot selects etc, nonetheless here i skip advantage involuntary joins, lazy-loading surrogate classes devaluate maintain bid list gets new buttress column gets renamed. (updating countless select, insert update queries vs. updating mapping config presumably refactoring business classes dtos.)

also, controlling nhibernate run non-static problems know horizon unequivocally well. be, example, guileless table.hbm.xml where set strings length automatically validated. however, i also suspect identical bugs simple sqlconnection query formed information opening layer.

finally, those arguments mentioned above unequivocally good reason utilize an orm non-trivial database formed craving application? there substantially arguments they/i competence have missed?

(i should substantially supplement i cruise initial big .net/c# formed concentration need teamwork. good practices, seen graceful normal smoke-stack , such section contrast continual integration, non-existing here adult now.)