Problem:

Upgrade Tips - StarTeam 4.2 to 5.2.

Resolution:

Information in this Brief applies to:

• StarTeam 5.2, StarTeam 4.2
• Windows NT, 2000

Overview

The following is a list of tips for upgrading from StarTeam 4.2 to StarTeam 5.2. For additional information, please see "Upgrading Server Configurations" in the StarTeam Installation Guide.

Details

1. It is recommended that you have the latest version of StarTeam 4.2 prior to the upgrade process. If you have a version of StarTeam 4.2 prior to Service Pack 3 (Build 4.2.742), you should upgrade to this version prior to attempting the 5.2 upgrade. StarTeam 4.2 SP3 can be downloaded from the following location if needed:

   ftp://customer:supportU$@12.13.2.122/StarTeam4.2Sp3/Starteam.exe

2. It is always recommended to have the latest updates for the 5.2 Server prior to upgrading as well. StarTeam 5.2 Service Pack 1 can be downloaded from the following location:

   http://www.borland.com/products/downloads/download_starteam.html

3. It is recommended that you first perform the upgrade in a test environment. This will help you determine the amount of time the upgrade procedure will take to help you with scheduled downtime. This also give you a chance to familiarize yourself with the process as well as determining if there will be any difficulties with the live upgrade. Please reference the following articles for assistance with moving/copying to a test environment:

   How To move a StarTeam repository with MS Access
   How to Move a StarTeam Repository with MS SQL

   Make certain that the Server starts under StarTeam 4.2 in the test environment to verify the that copy process was successful prior to attempting the upgrade operation.

4. If you are upgrading a Microsoft SQL Server or Oracle database, ensure that the Microsoft SQL Server or Oracle client is installed on the computer running StarTeam Server. You must also establish connectivity between the database server and the database client. For MS SQL Server, use the Enterprise Manager and Register a new SQL Server. For Oracle, use the Net8 Configuration Assistant. See your database?s documentation for details.

5. In releases prior to StarTeam 5.2, file status information was stored by the server in a database table. To improve performance, StarTeam now stores status information on the client workstation. Users can store this data centrally or on a per-folder basis. This is probably an individual decision. Please advise users to make their decisions and select the correct options when they use StarTeam for the first time after the installation or upgrade. Explanations of the two ways to store status can be found in the StarTeam User?s Guide.

   Before you upgrade the server, Borland recommends that you ask users to check in all the files that need to be checked in. Unless users move their file status information before the upgrade, all files will have the Unknown status because the file status table is no longer in the database. In most cases, the File\Update Status command can determine the actual status of the file, but it is best if the user already knows that everything of importance is Current. For example, files with the Merge status will remain Unknown even after the File\Update Status command runs.

   Users can move their file status information to their workstations prior to the server upgrade. Even if they do not, they need to decide where to store file status on their workstations. They can store it centrally (the default) or per-folder. They need to select one of the methods before opening projects and checking files in and out.

   See " Moving File Status Locally" for steps to move file status information to the client machine.

6. During the upgrade process tables are added to the database and the database more than doubles in size. With an Access database the upgrade may cease to function as the database reaches it?s functional limit in size. Please ensure that database is Access 2000 format or later before beginning the upgrade as its size limit is larger than previous Access versions. It may be necessary to repair and compact the DB on more than a single occasion and restart the upgrade process if these limits are reached.

7. You will need registration information specific to 5.2 to run the 5.2 products. You want to make certain you have this information available before upgrading. Your maintenance agreement needs to be current to obtain this information. Contact you Account Manager to move forward to obtain this information.