LINQ-to-SQL vs stored procedures, What's the best pratice?

I ran acrossed this new "LINQ-toSQL" thing, It's pretty amazing, but my question is, What's the best pratice in the real world that people used? It seems like using LINQ will embed all the Business Logic into the code, instead of keeping on the Database side(Stored Proecedure)? Isn't it harded to maintain them in the future? People told me we shuold keep most of the BL part in the SP, then inside the code. If that's true, what's the point of LINQ-SQL... Need some advice here.
cj_skywalkerAsked:
Who is Participating?
 
ralmadaCommented:
LINQ is something new, so you will find mixed opinions. But, I say it depends on what are your requirements.

There's a discussion here that will answer your questions:

http://stackoverflow.com/questions/14530/linq-to-sql-vs-stored-procedures

My main concern with linq is performance. as mentioned in the link

>>Network traffic: sprocs need only serialize sproc-name and argument data over the wire while LINQ sends the entire query. This can get really bad if the queries are very complex. However, LINQ's abstraction allows Microsoft to improve this over time. <<
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.