Ok, I'm probably being dumb, but I can't find a summary saying 'here is the new stuff you can do in T-SQL in Denali'.
There is obviously NEXT VALUE FOR, and support for paging - but is there a definitive 'this is what's new' post somewhere?
asked Dec 03, 2010 at 08:18 AM in Default
Matt Whitfield ♦♦
I liked this concise article from Aaron Bertrand.
For example, dual monitor support is new.
One part that's missing, at least so far according to Aaron, is the "bread crumb" feature that let's us click on an error message and it takes you to the error in the sproc. I especially liked that feature! ;0)
[Edit] The link mentioned above is hardly comprehensive. At times I wonder if I have reading comprehension problems! Anyway, you may have seen this and it doesn't claim to be an exhaustive list, but maybe this is more relevant to what you're asking.
In fairness Mark, I have written many blog posts focusing on different features introduced in Denali, including one on THROW. My list isn't comprehensive yet either (for example, I haven't yet blogged about AlwaysOn or the FMTONLY replacements). Here are a couple of links that might be useful to Matt.
This is a list of all the posts I've written and tagged with "denali" - this includes a slide deck of a "What's New in Denali" presentation I gave for the Philadelphia SQL Server User Group this week:
And here is an article on THROW specifically (which, as has been noted, did not make it into the CTP1 Books Online):
Just to clear up any misunderstanding, the Books Online process is not a simple "just throw a web page up there." In can often take weeks or longer to publish a simple page, since it has to be updated in several other places (all deep links, table of contents, index, etc) and it also has to be translated (the CTP and Books Online ship in more than just English). Not saying THROW shouldn't be there, but during the early beta phase we have to compromise. If it's a choice between getting the product with some docs missing, and waiting for complete docs (which will never happen during dev, because dev and doc do not move at the same speed), I know what I would vote for.