tag:blogger.com,1999:blog-4214922889450630344.post2482102627266714910..comments2008-06-09T18:15:42.355-07:00Robin Clowershttp://www.blogger.com/profile/09558658468617627887noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-4214922889450630344.post-87176742091706544142008-06-09T18:15:00.000-07:002008-06-09T18:15:00.000-07:00Hi merlin, thanks for your comment. I started to refute your argument in this comment, but it turned into a whole <A HREF="http://robinclowers.blogspot.com/2008/06/stored-procedures-best-practice.html" REL="nofollow">post</A>. If you have a minute, please check it out.Robin Clowershttp://www.blogger.com/profile/09558658468617627887noreply@blogger.comtag:blogger.com,1999:blog-4214922889450630344.post-18431296614877176572008-05-31T07:45:00.000-07:002008-05-31T07:45:00.000-07:00Even though the designer allows tables to be used, it is still considered best practice to use stored procedures. LINQ to SQL does highly optimize the SQL code, but it must still be compiled by the SQL Server before execution (not to mention the fact that calling on tables uses deferred execution).<BR/><BR/>Stored procedures allow the sql commands to be compiled and optimized on the SQL Server itself, which will result in faster execution. Also, sprocs can query multiple tables, databases, and servers.<BR/><BR/>Philip<BR/><A HREF="http://www.linqexchange.com" REL="nofollow">LINQ Exchange - Learn LINQ and Lambda Expressions</A>merlin981http://www.blogger.com/profile/05516602905783627586noreply@blogger.com