Kevin, if the solution was once added to version control and then deleted the warehouse will contain those two events because version control provides the checkins for the add and the delete. If you look at the Code Churn measure in the cube those two events should cancel each other so they should contribute 0 lines to your current total.

Can you describe how are you looking at the Code Churn measure, is it in one of the reports or in Excel?

Thanks

Federico

My understanding of code churn (http://msdn2.microsoft.com/en-us/library/ms244698.aspx) is that it is calculated by [Lines Added] + [Lines Deleted] + [Lines Modified].

So having 3 or 4 failed migrations that needed to be redone ends up with a report like this:

Alias	Lines Added	Lines Deleted	Lines Modified	Total Churn	Total Lines	Code Churn Count
A
	194750	116953	36298	348001	77797	6147
B
	1667	603	725	2995	1064	76
THIS IS MY ENTRY
	516955	431007	102022	1049984	85948	18029
C
	28995	8318	8792	46105	20677	906
D
	56574	7122	5955	69651	49452	1525
E
	10742	3601	5650	19993	7141	507

The problem is that this particular solution doesn't even contain 200,000 lines of code but because of the 1st few failed migrations the reports will now show my total churn of over 1,000,000 lines.

The calculation is accurate but isn't what we want. There really should be a way to recover from this kind of scenario w/o having to completely remove the whole team project. I'm thinking that some sort of administrator level permanent removal tool or some way to set a folder to not count against statistics in the cube. BTW - the report above is a custom report that is simply checked in alias by the 6 variables listed above.

Hi Kevin,

I understand your problem and I can tell you that even if you delete the entire Team Project and rebuild the entire Warehouse those entries will still be there because the version control system doesn't remove them from its history, you will still have the changeset/s that added them and the changeset/s that deleted them. So because this data is going to be in the Warehouse anyway your only option is to filter it out in the Report.

There are several different ways you can filter it out. If this data is in a different team project that was deleted then you can exclude that project, if this data is on a different folder path you can exclude those or if you know the changests that were used for the add and the deletion you can exclude those. If you are using Excel pivot tables to create your report you just need to add any of these to the filter area and deselect/select the proper values.

Federico