What are the pros and cons of using linq queries(along with an ORM like EF or linq2sql) VS. Stored Procedures(SQL server 2008) to query and update a data model? Performance? Speed? Etc…
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Linq is definitely more readable when you’re in the code. Seeing a call to execute a sproc called “sp_GetSomething” doesn’t tell you anything as a developer, unless you go and physically look at what the sproc does. seeing code like
That tells you exactly what data is being pulled.
Stored procedures on the other hand do not require you to recompile the application if you decide to change the code. If you decide to suddenly change a “
where” clause or change theOrder By– changing a sproc is easy. Changing the Linq code could be more time consuming.I’m sure there are plenty more, but these are two I’ve noticed.