title: NHibernate on legacy DB
body: <p>I'm ashamed to say it, but I have to. I have not worked with ORM's. I'm really considering NHibernate as it seems to be the most mature product for .Net out there (please correct me if I'm wrong). Now, the thing is that we have a big e-commerce/booking system with an SqlServer as the main integration point, containing quite a lot of business logic in sprocs. Now - obviously - this architecture is something we want to move away from, and we've been doing so for some time, piece by piece. So, my real question is how feasible is it to start using NHibernate for new features and not going back and map all the legacy stuff? Is this kind of gradual introduction of and ORM supported, and if so, would you recommend it?</p>