LINQ-to-SQL vs stored procedures?

Posted by scottmarlowe on Stack Overflow See other posts from Stack Overflow or by scottmarlowe
Published on 2008-08-18T12:37:57Z Indexed on 2010/05/04 13:28 UTC
Read the original article Hit count: 269

I took a look at the "Beginner's Guide to LINQ" post here on StackOverflow (http://stackoverflow.com/questions/8050/beginners-guide-to-linq), but had a follow-up question:

We're about to ramp up a new project where nearly all of our database op's will be fairly simple data retrievals (there's another segment of the project which already writes the data). Most of our other projects up to this point make use of stored procedures for such things. However, I'd like to leverage LINQ-to-SQL if it makes more sense.

So, the question is this: For simple data retrievals, which approach is better, LINQ-to-SQL or stored procs? Any specific pro's or con's?

Thanks.

© Stack Overflow or respective owner

Related posts about LINQ

Related posts about linq-to-sql