Comments on: Speeding up data access by using Linq to SQL or EF http://www.ytechie.com/2009/10/speeding-up-data-access-by-using-linq-to-sql-or-ef.html Productive software development using ASP.NET, C#, Adobe Flex, and other technologies and tools. Thu, 09 Sep 2010 10:53:34 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: Ta4ka http://www.ytechie.com/2009/10/speeding-up-data-access-by-using-linq-to-sql-or-ef.html/comment-page-1#comment-1698 Ta4ka Thu, 04 Mar 2010 12:35:30 +0000 http://www.ytechie.com/2009/10/speeding-up-data-access-by-using-linq-to-sql-or-ef.html#comment-1698 In your 3 point you say: If the underlying provider has an optimization for using the SQL TOP command, I have a linq to sql querry where I use it for paging and with take and skip, and orderby. When i execute the querry it takes more than 40 secounds. Can you tell me please how to turn optimization on, in the generate sql from linq. My sql server is mssql 2008 In your 3 point you say: If the underlying provider has an optimization for using the SQL TOP command,
I have a linq to sql querry where I use it for paging and with take and skip, and orderby. When i execute the querry it takes more than 40 secounds. Can you tell me please how to turn optimization on, in the generate sql from linq. My sql server is mssql 2008

]]> By: admin http://www.ytechie.com/2009/10/speeding-up-data-access-by-using-linq-to-sql-or-ef.html/comment-page-1#comment-1628 admin Wed, 28 Oct 2009 19:42:38 +0000 http://www.ytechie.com/2009/10/speeding-up-data-access-by-using-linq-to-sql-or-ef.html#comment-1628 I must have have explained it well enough. Actually think about what the stored procedure would look like. To truly optimize it, I mentioned that you would need 3 versions for EACH set of parameters: 1. Count 2. Page n 3. First page On the page I worked with, there were about 15 search criteria. That gives you 45 different stored procedures to be "optimal". The LINQ solution comes pretty darn close to that efficiency, while having no duplicate code. Is that clear now? I must have have explained it well enough.

Actually think about what the stored procedure would look like. To truly optimize it, I mentioned that you would need 3 versions for EACH set of parameters:
1. Count
2. Page n
3. First page

On the page I worked with, there were about 15 search criteria. That gives you 45 different stored procedures to be “optimal”. The LINQ solution comes pretty darn close to that efficiency, while having no duplicate code.

Is that clear now?

]]> By: Lek http://www.ytechie.com/2009/10/speeding-up-data-access-by-using-linq-to-sql-or-ef.html/comment-page-1#comment-1627 Lek Wed, 28 Oct 2009 19:33:11 +0000 http://www.ytechie.com/2009/10/speeding-up-data-access-by-using-linq-to-sql-or-ef.html#comment-1627 Hi, no doubt that Linq is a good tool, but I am sure that the stored proc you have take for your test was not really well wrotten, so that is why it seems to you that linq is faster... It is not possible at all in fact, because when using Linq a query is constructed internally and finally that is SQL which is produced and sent to the database server... A dba would not construct his statement using different if but would rather bind his parameters and make single sql statement in order to gain performance on the query plan... If you observe the sql generated by Linq it's pretty sure that all the parameters are bind parameters... In all case, reading your article, it seems that Linq have other advantages. I would use it in order to have only one language and not mixing stored procedure and c# code... But for very heavy database job I think that nothing could be better than a well written procedure... Hi,
no doubt that Linq is a good tool, but I am sure that the stored proc you have take for your test was not really well wrotten, so that is why it seems to you that linq is faster… It is not possible at all in fact, because when using Linq a query is constructed internally and finally that is SQL which is produced and sent to the database server…
A dba would not construct his statement using different if but would rather bind his parameters and make single sql statement in order to gain performance on the query plan…
If you observe the sql generated by Linq it’s pretty sure that all the parameters are bind parameters…
In all case, reading your article, it seems that Linq have other advantages. I would use it in order to have only one language and not mixing stored procedure and c# code… But for very heavy database job I think that nothing could be better than a well written procedure…

]]> By: 9eFish http://www.ytechie.com/2009/10/speeding-up-data-access-by-using-linq-to-sql-or-ef.html/comment-page-1#comment-1625 9eFish Wed, 28 Oct 2009 10:07:16 +0000 http://www.ytechie.com/2009/10/speeding-up-data-access-by-using-linq-to-sql-or-ef.html#comment-1625 <strong>使用Linq to Sql 或者 EF加快数据访问速度...</strong> 9efish.感谢你的文章 - Trackback from 9eFish... 使用Linq to Sql 或者 EF加快数据访问速度…

9efish.感谢你的文章 – Trackback from 9eFish…

]]>