In my last post, I wrote about the relational warehouse and cube schema changes coming your way in TFS 2010. We just released 2010 Beta 2 and I wanted to outline additional schema changes we have made in the cube, especially to polish it for final release and also address a few key usability aspects.
Here’s a comparison between TFS 2008, TFS 2010 Beta 1 and TFS 2010 Beta 2:
TFS 2008 TFS 2010 Beta 1 TFS 2010 Beta 2
Here are the main changes to the Team System cube in Beta 2:
Probably one of the biggest changes that we have made in this category is to collapse the ‘Work Item History’ and ‘Current Work Item’ measure groups into one ‘Work Item’ measure group which dynamically shows trend if you include Date and current data otherwise.
Old Dimension Name New Dimension Name File Version Control File Changeset Version Control Changeset Configuration Test Configuration Linked Work Item Work Item Linked Source Project File Build Source Project File Work Item Test Case Test Case
Old Measure Name New Measure Name Cumulative Build Result Count Build Result Count Trend Cumulative Point Count Point Count Trend Cumulative Result Count Result Count Trend
One last thing I wanted to call out isn’t related to cube schema, but we have changed the name of the Analysis Services database we create by default. The name of database is ‘Tfs_Analysis’. We want to straighten out the terminology instead of overloading the term warehouse to mean both the relational warehouse database as well as the analysis database. Of course, this is just the default and in 2010 you get the flexibility to name this database however you like using Team Foundation Administration Console.
If you have any questions or feedback please leave me a comment of send me an email at sunder.raman at microsoft.com.
[Update 10/21/2009] John Socha-Leialoha has written detailed blog posts, Part 1 and Part 2, to help upgrade custom reports written against TFS 2008 to work with the new schema changes I outlined in this post.