TrentNix

I went through the steps of recreating the data warehouse from the command line using SetupWarehouse and have an issue. All of the work item data populates in the TFSWarehouse relational table as I expect, but the [Code Churn] table and the [Work Item Changeset] table are out of sync.

I have a report that takes a work item, tunnels through and finds all changesets associated with it. Then, it tunnels down and finds all of the files associated with those changesets, thus giving all of the files that are 'associated' with that work item. Now that I have rebuild the warehouse, this report no longer shows valid data.

Joining [File] and [Code Churn] works as I expect, but when I join [Code Churn] and [Work Item Changeset] (on [Code Churn].Changeset = [Work Item Changeset].Changeset), no dice.

Here is my query:

SELECT [File].[File], Churn.Changeset

FROM [File]

INNER JOIN [Code Churn] AS Churn ON Churn.Filename = [File].__ID

INNER JOIN [Work Item Changeset] AS WICS ON Churn.Changeset = WICS.Changeset

Help!

It should be noted that [Work Item], [Current Work Item], and related tables are fine and all reports that use them work as expected.



Re: Team Foundation Server - Reporting & Warehouse [Code Churn] and [Work Item Changeset] out of sync

TrentNix

One additional note, this is using TFS 2008 B2.





Re: Team Foundation Server - Reporting & Warehouse [Code Churn] and [Work Item Changeset] out of sync

Dave McKinstry

Trent - Since I know directly the specifics of your situation I'm going to add a little more context and maybe you can fill in more as well...

  1. The place you're working has been using TFS 08 Beta 2 with VSTS/Team Explorer 05 successfully for a couple months.
  2. The query and report you're speaking of has been working fine during much (most ) of that time.
  3. At some point it stopped working. Now for you to fill in the blanks. I think that all of the reports died and a rebuild seemed like the obvious solution. And it is working somewhat but this data in specific is NOT coming back from the grave.

Is that right Can you add more context





Re: Team Foundation Server - Reporting & Warehouse [Code Churn] and [Work Item Changeset] out of sync

TrentNix

The process template was modifed to add additional fields to the warehouse. Since those fields are only pushed to the warehouse in the case of a specific work item changing, I needed to get all of the newly reportable data pushed to the warehouse. That is what catalyzed a warehouse rebuild.

That process was successful...that data is now in the warehouse and the newly added reports with the newly reportable fields are happy. The existing report that uses churn data is not.

The relationships on the work items themselves exist and are fine.

I think that the data is coming back, it just is not synchronized between [code churn] and [work item changeset] (which uses the [changeset] table as a go-between).





Re: Team Foundation Server - Reporting & Warehouse [Code Churn] and [Work Item Changeset] out of sync

Larry Bynum - msft

Hi Trent, are you still experiencing this issue Please let me know, I have a few questions and some things you can try out for me.

Thanks,

-Larry






Re: Team Foundation Server - Reporting & Warehouse [Code Churn] and [Work Item Changeset] out of sync

TrentNix

Larry,

The issue has been resolved. Ultimately, there wasn't really an issue. It was simply taking a long time to process work item <--> changeset links. From discussions I had elsewhere, this was an issue with the pre-2008 RTM. Additionally, the adapters were set to refresh every 15 minutes and it would halt work item<-->changeset processing in order to process the warehouse adapters, thus giving the impression that the rebuild was complete.

Eventually the data found its way back into the database and all is well. The issue of the processing time has been fixed by MSFT in the RTM.

Thanks for your assistance.





Re: Team Foundation Server - Reporting & Warehouse [Code Churn] and [Work Item Changeset] out of sync

Larry Bynum - msft

Thanks Trent for the Reply!

-Larry