http://www.sqlservercentral.com/blogs/andy_warren/archive/2008/02/05/what-s-wrong-with-linq-to-sql.aspxThere&#39;s a lot of buzz in the development community about LINQ in general, and for those that do data access just as much buzz about Linq to SQL. It&#39;s hard to describe in a sentence, but think of LINQ as a way to write queries against .Net objectsenCommunityServer 2007.1 (Build: 20917.1142)http://www.sqlservercentral.com/blogs/andy_warren/archive/2008/02/05/what-s-wrong-with-linq-to-sql.aspx#12187Mon, 08 Jun 2009 12:55:31 GMT70975365-724d-4ce8-8d1c-45c963ab81ff:12187Andy Warren<p>Jim, I'll try to make time to look at that. Thanks for the follow up!</p> <img src="http://www.sqlservercentral.com/blogs/aggbug.aspx?PostID=12187" width="1" height="1">http://www.sqlservercentral.com/blogs/andy_warren/archive/2008/02/05/what-s-wrong-with-linq-to-sql.aspx#12174Sun, 07 Jun 2009 20:10:33 GMT70975365-724d-4ce8-8d1c-45c963ab81ff:12174Jim Wooley<p>You may want to take a look at the enhancements coming with VS 2010. It appears that they are fixing the third issue you complained about - bloated query plan caches. They are fixing the parameter lengths for the next release.</p> <img src="http://www.sqlservercentral.com/blogs/aggbug.aspx?PostID=12174" width="1" height="1">http://www.sqlservercentral.com/blogs/andy_warren/archive/2008/02/05/what-s-wrong-with-linq-to-sql.aspx#8340Sun, 10 Feb 2008 13:15:40 GMT70975365-724d-4ce8-8d1c-45c963ab81ff:8340Arthur Fuller<p>I too am uneasy about Linq to SQL, and in particular about the short-shrift that stored procedures and table UDFs seem to be receiving. I'm old-school, perhaps; I have come to believe that anything the back end can do, the back end should do.</p> <p>I'll keep learning it, but I'll fill the perceived gap by placing my focus on using sprocs and udfs with Linq.</p> <p>Arthur</p> <img src="http://www.sqlservercentral.com/blogs/aggbug.aspx?PostID=8340" width="1" height="1">