Is linq down my SQL server performance?

Question

0.00/5 (No votes)

See more:

SQL-Server-2012

few days back i have changed the CRUD operations code . entity framework SP to LINQ.
now i can able to see frequent sql server block. let me know why?

is linq insert or concurrent linq insert make my Database performance?

What I have tried:

once the performance based sql server utilisation high or CRUD via linq with concurrent users its make sense. i really don't understand

Posted 12-Oct-16 0:39am

sencsk

Updated 12-Oct-16 1:04am

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

F-ES Sitecore · Answer 1 · 2016-10-12T01:03:00

If there was no compelling reason to use LINQ then go back to SPs if they work. If you've written a whole bunch of LINQ code without any consideration as to how the SQL is generated then the SQL you're running will be very different from SPs, there will be lots of table access you don't know about and all sorts.

If you are joining tables then make sure you're not using "lazy loading" (google "entity framework lazy loading"). You can also use tools like SQL Profiler to see the SQL being generated.

At the end of the day though, just go back to SPs if they work. LINQ's advantages are around not having to write a lot of SQL yourself but you have to be mindful of how you're asking EF to generate the SQL, it's a big subject outside the scope of a forum post. Don't think LINQ is a panacea that gives you better performance etc as well as easier code.