Wich dataaccess metod is faster - with datareader when the data is return from stored procedures or with LINQ

[Lyubomir Rumenov Velchev]

Wich dataaccess metod is faster - with datareader when the data is return from stored procedures or with LINQ. What is the difference if is working with milions of records in a table? Thanks for your answers!

[elizas]

Hi, Though I am not a technical person but found your post to be very informative. I would like to share a link where a Software Testing Engineer of my company (http://mindfiresolutions.com/[^]Mindfire Solutions) has done a very good analysis on http://mindfiresolutions.com/database-and-client-server-development.htm[^]database application. Hope you find it useful.

Cheers, Eliza Mindfire: India's Only Company to be both Apple Premier & Microsoft Gold certified.

[Ennis Ray Lynch Jr]

A properly used data reader will always be faster ... since it is of course the most direct method of accessing data in .NET. Data readers are even more efficient if you define indexes for the returned columns instead of using the string look-up method.

Need custom software developed? I do custom programming based primarily on MS tools with an emphasis on C# development and consulting. A man said to the universe: "Sir I exist!" "However," replied the universe, "The fact has not created in me A sense of obligation." --Stephen Crane

[Lyubomir Rumenov Velchev]

Do you how much faster it will be? Do you have any statistics for example table with 10 milin rows?

[Ennis Ray Lynch Jr]

I have a system which I currently maintain that I converted one report from LINQ to the Data reader method. The one report was estimated to have a run time of a week with LINQ (we never let it finish just did timings on subsets) and the data reader version takes 30 seconds. Admittedly the LINQ version could have been cleaned up but LINQ encourages bad code so that needs to be watched for as well. In general Data Readers with integer column indexes on well written stored procedures: fastest Data Readers with string column indexes on well written stored procedures: 10x slower LINQ 20x to 100x slower. Some situations LINQ will be just as fast as data readers but never faster. You can ignore the size of the database for the discussion. If you want statistics there is someone who did a nice little timing comparison between all of the methods (you can search Google if you want) or you can take my word for it.

Need custom software developed? I do custom programming based primarily on MS tools with an emphasis on C# development and consulting. A man said to the universe: "Sir I exist!" "However," replied the universe, "The fact has not created in me A sense of obligation." --Stephen Crane

[Not Active]

Look here[^]

---

I know the language. I've read a book. - _Madmatt

[Mycroft Holmes]

Ennis Ray Lynch, Jr. wrote:

The one report was estimated to have a run time of a week with LINQ

That is possibly a little unfair, I've had 1st draft stored procs that have run times of hours, after a little works and some indexing they get reduced to seconds. However your point that LINQ encourages lousy code by abstracting another layer is the telling point. How many devs get under the hood of the Linq, or are even capable of doing so! I'm of the opinion that LINQ is one of the greatest abominations ever to come out of MS.

Never underestimate the power of human stupidity RAH