It's been a busy news day!
First, there are some very interesting figures out comparing XML performance on .NET 2.0 against .NET 1.1 and also JVM 1.5, using benchmarks devised by Sun. The conclusion:
The XML Mark 1.1 Benchmark Kit demonstrates that major improvements have been made with .NET 2.0 over the .NET 1.1 runtime for XML parsing. These improvements will impact both client and server programs that do any amount of direct XML manipulation. Furthermore, the results indicate that .NET 2.0 performs significantly better than the latest Sun Java 1.5 platform in XML parsing scenarios. We encourage customers to download the XML Mark 1.1 benchmark kit and test the scenarios for themselves.
More .NET vs J2EE performance information is available for your analysis.
Also, Michael Rys summarizes Paul Flessner's keynote at Tech Ed about SQL Server 2005. The biggest news is a firm world-wide launch date, the week of November 7. The June Community Technology Preview is now available. Michael has another post summarizing its noteworthy XML capabilities.
Paul Flessner presented some SQL Server performance figures too:
TPC-C: 37% better perf at 17% lower cost than SQL Server 2000 numbers on HP 64-P Itanium hardware using scale up (hitting 1082203 T/S; 7% better than Oracle at 37% less cost)
TPC-H 1TB: 162% better at 54% less cost (on same platform again faster and cheaper than Oracle numbers)
Finally, it's probably not news for many of you that the next version of Microsoft Office will use XML as the default document format, but Brian Jones has a lot of details in his weblog. This is a Big Deal for many of us who have long dreamed of the day in which mainstream users will automatically create documents, spreadsheets, and presentations that can be processed and integrated by XML developers. Add this to the Metro display format, and the work by other vendors and standards organizations to build XML deeply into both the desktop and the infrastructure, and this has potentially to fundamentally change the way people work with information. Our next challenge at Microsoft is to go even farther to make all this XML easily usable by mainstream developers so that they -- you folks, really -- can bring the vision to reality.