We did get some great feedback on AdventureWorksLT @ the summit and some folks volunteered to begin doing work to make it what the community needs it to be. I'm going through the "key takeaways" from the AW vNext session this week. Filing work items @ CodePlex (and volunteering to do some of the work) are very much welcomed. We're ramping up to do the Kilimanjaro revisions to AW, etc.
For the record, we're willing to accept ideas on !AdventureWorks databases (that's NOT AdventureWorks for the T-SQL-only coders), too, especially if you're going to do the creative work.
Also note that the principal reasons that our brethren (and sistren) in DevDiv give for continuing to use Northwind instead of AdventureWorks are:
1. The Visual Studio tools don't support the "new" data types (some of which have been around since Yukon).
2. AdventureWorks is too complicated, too normalized, too not-Northwind.
If you don't like AdventureWorks (which is fine -- I won't take it personally), tell us what you'd rather see in terms of scenario, industry/vertical, whatever. I've asked lots before, and I'm still listening... http://msftdbprodsamples.codeplex.com/WorkItem/List.aspx
At the risk of starting another holy war, it's routinely alleged that AW "violates best practices". Tell me which are your pet "best practices" and how they're violated. It'll be fun to watch everyone else disagree.