Comments on: Why use LINQ to SQL? http://www.ashchuan.com/blog/2008/05/23/why-use-linq-to-sql/?utm_source=rss&utm_medium=rss&utm_campaign=why-use-linq-to-sql On software, gadgets, programming and blogging Tue, 31 Jan 2012 17:15:18 +0000 hourly 1 http://wordpress.org/?v=3.2.1 By: bakerdal http://www.ashchuan.com/blog/2008/05/23/why-use-linq-to-sql/comment-page-1/#comment-100125 bakerdal Sat, 08 Jan 2011 05:04:01 +0000 http://www.ashchuan.com/blog/2008/05/23/why-use-linq-to-sql/#comment-100125 I have been using Linq to SQL for a large project for the last couple of months. It is great for the strongly typed object model and its ability to query other types of data. But Linq to SQL/Stored Procedures does not perform as well as ADO.NET/Stored Procedures. There are a lot of great articles regarding performance tuning with Linq but the bottom line is that you have to jump through 25 hoops to get to 93% of a SQLDataReaders performance benchmark. I don't have the time or want to have to spend extra programming time and flip every switch to get a performance benchmark that is slower than older technology. For low traffic areas of the site I am using Linq to SQL (love it), but for high demands where every cycle counts I am sticking with good old Stored Procedures, Parameterized Queries and ADO... I have been using Linq to SQL for a large project for the last couple of months. It is great for the strongly typed object model and its ability to query other types of data. But Linq to SQL/Stored Procedures does not perform as well as ADO.NET/Stored Procedures. There are a lot of great articles regarding performance tuning with Linq but the bottom line is that you have to jump through 25 hoops to get to 93% of a SQLDataReaders performance benchmark. I don’t have the time or want to have to spend extra programming time and flip every switch to get a performance benchmark that is slower than older technology. For low traffic areas of the site I am using Linq to SQL (love it), but for high demands where every cycle counts I am sticking with good old Stored Procedures, Parameterized Queries and ADO…

]]> By: TriSys http://www.ashchuan.com/blog/2008/05/23/why-use-linq-to-sql/comment-page-1/#comment-79932 TriSys Wed, 09 Jun 2010 10:14:44 +0000 http://www.ashchuan.com/blog/2008/05/23/why-use-linq-to-sql/#comment-79932 LINQ cannot even handle LIKE operators - your example above Country Like 'A%' will cause a run-time error - proving that the LINQ team do not understand SQL LINQ cannot even handle LIKE operators – your example above Country Like ‘A%’ will cause a run-time error – proving that the LINQ team do not understand SQL

]]> By: Code Principles http://www.ashchuan.com/blog/2008/05/23/why-use-linq-to-sql/comment-page-1/#comment-7157 Code Principles Thu, 05 Jun 2008 18:34:16 +0000 http://www.ashchuan.com/blog/2008/05/23/why-use-linq-to-sql/#comment-7157 Wow, same here. .Net programmer, forced database administrator, and excellent T-SQL and PL/SQL writer. LINQ looks great for .NET objects, but for replacing SQL, I will learn it, but stick with my bread and butter. Wow, same here. .Net programmer, forced database administrator, and excellent T-SQL and PL/SQL writer.

LINQ looks great for .NET objects, but for replacing SQL, I will learn it, but stick with my bread and butter.

]]>