Hi,
The first upgrade I did was in a Virtual Machine, but the following Service Packs were applied before I started: SQL Server 2005 Service Pack 2 <http://www.microsoft.com/downloads/details.aspx?FamilyId=d07219b2-1e23- 49c8-8f0c-63fa18f26d3a&DisplayLang=en> Visual Studio 2005 Team Foundation Server Quiescence <http://www.microsoft.com/downloads/details.aspx?FamilyID=c18c756e-8f80- 4987-b3bf-600068a9e3c4&displaylang=en> Update for Windows Server 2003 (KB925336) <http://support.microsoft.com/kb/925336> Visual Studio 2005 Team Foundation Server Service Pack 1 <http://www.microsoft.com/downloads/details.aspx?FamilyId=A9AB638C-04D2- 4AEE-8AE8-9F00DD454AB8&displaylang=en> I have not tried a bare upgrade from v1.0 so I cannot comment on that. I agree with Jonathon in regards to the disk space, maybe relocate your TEMPDB database to another drive. Wes MacDonald From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of William Bartholomew Sent: Thursday, December 06, 2007 4:51 PM To: [email protected] Subject: RE: [OzTFS] Issues upgrading Team Foundation Server 2005 to 2008 Jonathan, Firstly, I can confirm that TFS 2005 SP1 is NOT required before installation. As far as tempdb growing is concerned, while I haven't had this cause an issue (the only machine I've done the upgrade on had a couple of hundred gigs free) I assume that the upgrade process is quite database intensive and a lot of these operations appear to be happening in the tempdb database which will cause it's log to grow until a transaction log backup is done. I would try to ensure that you have at least the same amount of free space as the size of your TFS databases plus a bit extra to be safe. Regards, William Bartholomew ________________________________ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jonathan Zack Sent: Friday, 7 December 2007 3:42 AM To: [email protected] Subject: [OzTFS] Issues upgrading Team Foundation Server 2005 to 2008 Hi, I did tons of up-front research and prep before attempting the installation including following each recommended step in this post <http://ozgrant.com/2007/11/24/tips-for-upgrading-from-tfs2005-to-tfs200 8/> . I was pretty optimistic considering that there are very few issues reported so far. I had never installed SQL Server 2005 SP1 on my single-box TFS machine so I installed it. Everything passed in the System Health Check afterwards. The installation process was fairly smooth and quick until the progress bar made it to just a little bit left and then it appears to just sit for over an hour. It basically looks like it sits until it depleted all of the room left on the C:\ drive of the server (which had 7 GB available at the beginning of the installation). After rerunning the installation a few times, I figured out that something was indeed going on behind the scenes and that the tempdb log was growing and growing (when the install finally failed, the tempdb log was 5 GB in size). The message box from the installation simply states, "Error 29250.Team Build Upgrade failed to complete successfully". I opened up the logs and the last couple of lines have this: Starting execution of steps from prereq01_PrepareUpgrade.sql.resources Finished execution of steps from prereq01_PrepareUpgrade.sql.resources Starting execution of steps from step01_MigrateBuilds.sql.resources Finished execution of steps from step01_MigrateBuilds.sql.resources Starting execution of steps from step02_MigrateBuildQualities.sql.resources Finished execution of steps from step02_MigrateBuildQualities.sql.resources Starting execution of steps from step03_MigrateBuildSteps.sql.resources Finished execution of steps from step03_MigrateBuildSteps.sql.resources Starting execution of steps from step04_MigrateAssociatedChangesets.sql.resources Finished execution of steps from step04_MigrateAssociatedChangesets.sql.resources Starting execution of steps from step05_MigrateAssociatedWorkItems.sql.resources Finished execution of steps from step05_MigrateAssociatedWorkItems.sql.resources Starting execution of steps from step06_MigrateOpenedWorkItems.sql.resources I then cleaned up the C:\ drive to have 13 GB of disk space available and reran the installation. It still took a long while and depleted all of the space on the C:\ drive but made it one step further to "step07" (I don't have the text in front of me but I believe it mentions migrating Projects or something). So I am now on my 7th run of the installation. This time, I have setup SQL Server to create the tempdb files on a separate drive which has 26 GB available. It has been running for a while and has depleted 7 GB of disk space. All of this seems a bit crazy. Why would the logs be growing like this? One important thing to note is that I never installed TFS 2005 SP1 on this machine but I don't know why this would make a difference (it wasn't flagged in the System Health Check either). Any help would be greatly appreciated. Regards, JZ OzTFS.com - to unsubscribe from this list, send a message back to the list with 'unsubscribe' as the subject. View the web archives at http://www.mail-archive.com/[email protected]/ Powered by mailenable.com, supported by www.readify.net OzTFS.com - to unsubscribe from this list, send a message back to the list with 'unsubscribe' as the subject. View the web archives at http://www.mail-archive.com/[email protected]/ Powered by mailenable.com, supported by www.readify.net OzTFS.com - to unsubscribe from this list, send a message back to the list with 'unsubscribe' as the subject. View the web archives at http://www.mail-archive.com/[email protected]/ Powered by mailenable.com, supported by www.readify.net
