My colleague James has been hassling me for not posting anything of use to him...
A long time ago in a land far far away there was a cunning plan to develop a new file system around a database called WinFS. This created quite a lot of positive reaction and there was a lot of flak when the project was taken out of Windows server 2008. I am not going to argue the rights and wrongs of the approach or the decision to abandon it, but in my opinion that capability is alive and well and inside SQL server 2008.
One of the goals of SQL server 2008 is "beyond relational". This will show up in a number of the features:
Add to this the access privileges that work in much the same way and inter-operate with active directory and the the fact that SQL server is behind SharePoint.
So SQL Server 2008 - a file system within an operating system.
Ooooh I love friendly jibes amongst the team :-)
Can you post a more detailed SQL 2008 vs. WinFS list? I'm more curious about the WinFS specific features such as rich relationship types, RAVs, rules, native store support for complex schemas (vs. EF mapping to standard SQL tables). I have heard bits and pieces about how SQL 2008 is going to be great for the Entity Framework however all of the EF features I've seen so far work fine with SQL 2005 (maybe I've missed some features). Is SQL 2008 going to include some of the WinFS functaionlity I mentioned above and/or add richer functionality to EF? I keep hearing "WinFS is alive and well in ADO.NET and SQL Server." However, EF is not WinFS and the major SQL 2008 features I've read about also are not what made WinFS attractive.
I, as many were, was very excited about WinFS and was disappointed when it seemed to fizzle out. I feel like I'm being teased by hearing anything about WinFS.
Not sure what features you are missing, I did also find this post about winFS http://blogs.msdn.com/winfs/archive/2006/06/23/644706.aspx
and I know the team that were doing the work are the same people doing Filestream and the Remote Binary Storage features.