Upgrade from B3R to RTM: Possible database upgrade issue.
After we upgraded from B3R to RTM, all Microsoft created Work Items, Queries and Reports work perfectly, and all our Work Item customizations work perfectly, as well. B3R was our initial installation version.
That said, we ran into an issue with some of Conchango's SCRUM for TeamSystem reports that utilize the Work Item History field.
It seems that the TfsWarehouse>Work Item History>Date field was not upgraded from type int to type datetime when we ran the TFSUpgrade.exe. We verified that it is typeint in our database, and Conchango has verified that thiers is typedatetime, and this is why their reports are not running in our installation.
The nice folks at Conchango believe that this field should have been modified during the upgrade. They did not follow the upgrade path, but rather installed the RTM version from scratch, so they did not run into this circumstance in their development environment.http://scrumforteamsystem.com/cs/forums/41/ShowPost.aspx "Problem with some reports"
We thought we had successfully completed the Upgrade since there were no errors anywhere during execution of the upgrade, even the upgrade log files are clean.
1. Can you please verify whether the correct Type for the TfsWarehouse>Work Item History>Date field is int or datetime?
2. If it is supposed to be datetime, can you provide us with instructions / tools, etc to properly upgrade this field from int to datetime (and the production data that's in it)?
3. Assuming there was an error, how can we verify that upgrade was truely successful and that there are no other errors of this type that will haunt us in the future?
Thanks, Dan
QA Manager / SCRUM Master
Brandwise, Inc.
[1970 byte] By [
dbreggin] at [2007-12-20]
I discussed this with a developer who has worked on the upgrade utility: When you run TfsUpgrade.exe, the relational warehouse is dropped. The system then relies on the RTM setup to set up the new databse with the appropriate fields.
In the RTM Warehouse, the field you are referencing above should be of type datetime. I am not sure on the reason why the database is in its current state(this will require more information and investigation...).
Now one thing you can do in order to obtain the latest version of the warehouse is to rebuild it by running SetupWarehouse.exe with the -rebuild flag. This will drop the database, rebuild it and populate all the data from the OLTP databases and then recreate the cube and process it. Rebuilding the warehouse might take some time depending on the amount of data in your TFS system(See http://msdn2.microsoft.com/en-us/library/ms400783.aspx for more information about SetupWarehouse).
Thanks,
Othmane
This did not solve our problem.
The field is still int: Date(FK, int, null)
The date/size of the warehouseschema.xml is Wednesday, January 25, 2006, 11:50:50 PM, 63.7 KB (65,237 bytes) Is this the right one? Does the FK impact the type?
Thanks, Dan
FYI: I had to go to http://msdn2.microsoft.com/en-us/library/ms252458.aspx to get complete instructions on how to use the SetupWarehouse.exe tool. I did everything here except backup/restore databases.
FK just points out that it is a foreign key, it gets its type from the field __ID of the dbo.Date dimension table.
The Date type change is not applied from the xml but rather in the SetupWarehouse.exe, What is the version number of SetupWarehouse that you are using? and its date/size?
Also, could you confirm that you ran a "SetupWarehouse.exe -rebuild" and not "SetupWarehouse.exe -o"?
Thanks,
Othmane
setupwarehouse.exe version 8.0.50727.127
236 KB (241,664 bytes)
Thursday, February 02, 2006, 3:03:52 AM
Confirmed used this command:
setupwarehouse -rebuild -s hqtfs -d tfswarehouse -c warehouseschema.xml -a brandwise\tfsservice -ra brandwise\tfsreports
Since I ran this yesterday, all (even microsoft) reports fail to run (there is no data in the warehouse) and the Date field type is not changed.
You have the RC bits rather than the RTM ones. As:
8.0.50727.43 = Beta 3 Refresh
8.0.50727.127 = RC
8.0.50727.147 = RTM
In RC, the Date field was still of type integer, so the Setupwarehouse rebuilt it correctly.
Now, I would recommend upgrading to the latest version of TFS: RTM, in order to have the latest bits and be able to use the Scrum Methodology reports.
In case, you do not wish to do so at the moment, please provide me with more information on the report failure (What do you see when you run the reports? Are there any errors in the event log?...) as to better understand the issue.
Thanks,
Othmane
