<p>Linq To SQL or Entity framework both integrate nicely with SQL Server 2005.</p>

<p>The SQL Server 2008 spec sheet promises even better integration - but I can't see it.</p>

<p>What are some examples of what you can do Linq-wise when talking to a 2008 server that you can't when talking to SQL Server 2005?</p>

[{'answer_id': 15431, 'author': 'Darren Kopp', 'author_id': 77, 'author_profile': 'https://Stackoverflow.com/users/77', 'pm_score': 0, 'selected': False, 'text': '<p>it has full support for the new data types. lol. beyond that you got me, other than possibilities of optimised queries (like the merge command, etc).</p>\n'}, {'answer_id': 15441, 'author': 'Nick Berardi', 'author_id': 17, 'author_profile': 'https://Stackoverflow.com/users/17', 'pm_score': 0, 'selected': False, 'text': "<p>I am guessing most of it has to do on the server anyways.  They probably optimized the query execution as for differences I don't know except for the new types.</p>\n"}, {'answer_id': 153273, 'author': 'Amy B', 'author_id': 8155, 'author_profile': 'https://Stackoverflow.com/users/8155', 'pm_score': 1, 'selected': False, 'text': '<p>There is a problem of paging over a joined set that SQL 2005 mis-interprets.</p>\n\n<pre><code>var orders = (\nfrom c in Customers\nfrom o in c.Orders\nselect new {c, o}\n).Skip(10).Take(10).ToList();\n</code></pre>\n\n<p>LINQ generates a ROW_Number against the joined set.  SQL2005 generates a bad plan from that code.  Here\'s a link to the <a href="http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=3091519&amp;SiteID=1" rel="nofollow noreferrer">discussion</a>.</p>\n\n<p>Edit#2:  I\'d like to clarify that I don\'t know that SQL2008 solves this problem.  I\'m just hopeful.</p>\n'}, {'answer_id': 153408, 'author': 'Amy B', 'author_id': 8155, 'author_profile': 'https://Stackoverflow.com/users/8155', 'pm_score': 1, 'selected': False, 'text': '<p>This <a href="http://www.microsoft.com/sqlserver/2008/en/us/linq.aspx" rel="nofollow noreferrer">marketing link</a> claims</p>\n\n<p>"Write data access code directly against a Microsoft SQL Server database, using LINQ to SQL."</p>\n\n<p>Which is basically untrue.</p>\n\n<p>Linq To SQL is query comprehension translated into expression trees translated into SQL, optimized by the query optimizer and then run against SQL Server database.  "directly" feh.</p>\n'}, {'answer_id': 3653486, 'author': 'gbn', 'author_id': 27535, 'author_profile': 'https://Stackoverflow.com/users/27535', 'pm_score': 0, 'selected': False, 'text': '<p>Unless LINQ exposes the new MERGE statement, no.</p>\n\n<p>There is little effective difference in the engines especially from an ORM/client view</p>\n'}]
['https://Stackoverflow.com/questions/15395', 'https://Stackoverflow.com', 'https://Stackoverflow.com/users/1855/']