title: Which ORM supports mapping existing databases?
body: <p>So I have a layered ASP.NET MVC proof-of-concept application with good separation between presentation concerns, business logic, and infrastructure concerns.  Right now it is operating off of a fake repository (i.e. LINQ queries against static IQueryable objects).  I would like to create a functional SQL repository now.</p>
  
  <p>That said, I don't want to simply tie it into a database that has a 1-1 mapping between tables and entities.  That wouldn't meet the business need I am hoping to solve (partial integration with existing database - no hope for convention over configuration).</p>
  
  <p>Do you have suggestions for which ORM / mapping tools I should consider and/or avoid?<br>
  Do you have suggestions for articles/books I could look at to help me approach this topic?</p>
  
  <p>Would it be better to simply use parameterized queries in this scenario?</p>