Performance Maintenance for Starteam with a SQL Server Backend



Performance Maintenance for Starteam with a SQL Server Backend


  • Product Name: StarTeam
  • Product Version: 2006-2008
  • Product Component: SQL Server Scripts
  • Platform/OS Version: All Supported OS


Performance in Starteam has been improved for all users with larger teams in mind, maintenance choices for Starteam performance has also been improved. Listed below are some of the choices.


~~~~~~~~~~~~~~~~~Important ~~~~~~~~~~~~~~~~~

Before running any of the StarTeam SQL scripts for a Microsoft SQL Server or MSDE database, ensure that the database compatibility mode is set correctly. For Microsoft SQL Server 2000-based configurations, set the database compatibility mode to 80.

Shut down the StarTeam Server before running any database script. The database may become corrupted if StarTeam users access it while a script is running.

Be sure to backup your StarTeam database, as necessary, and verify these backups periodically. You should restore and test backups of your StarTeam project data on a test system. Restoring and testing your backups helps to ensure that your data is being backed up correctly.

Starteam Engineering has provided some SQL Scripts for Microsoft SQL Server and MSDE that can be run individually as needed or scheduled to run by SQL Server on a regular basis. These scripts help you maintain and tune StarTeam databases. You run some database scripts after installation, some on a weekly basis for database performance maintenance, and some scripts are run for you automatically by StarTeam Server. The Microsoft SQL Server database scripts are located in the StarTeam Server XXXX\DBScripts\Sqlserver_Scripts.

The Sqlserver_scripts folder contains four subfolders:

  • Create Stored Procedures
  • Drop Stored Procedures
  • Install
  • PreInstall
The scripts in these folders are run by StarTeam Server as needed. Do not execute any of these stored procedures directly from an external database user interface, such as SQL Query Analyzer.

The list below outlines the scripts that you should run manually and recommends the frequency for running these scripts. You may choose to adjust the frequency depending on the StarTeam usage at your facility. You may adjust the frequency depending on the StarTeam usage at yourfacility. Run scripts at times when the server is least used, such asovernight or on weekends.

In addition to running the scripts outlined, you should also use the Purge option on the Server Tools utility to remove deleted views from the database. We recommend purging the database after you have deleted one or more views from a StarTeam project. See StarTeam Administrator?s Guide for more information on the Purge option.

Recommended SQL Server maintenance scripts:

starteam_sqlserver_dbcc --->should be scheduled to run weekly.
starteam_sqlserver_dbcc_reindex --->should be scheduled to run twice a week (minimum)
starteam_sqlserver_dbcc_showcontig --->should be scheduled to run twice a week (minimum)
starteam_sqlserver_dropall --->should be run ONLY if necessary
starteam_sqlserver_tuning_script --->should be run after migrating a database:

For more detailed information regarding running SQL Scripts for Microsoft Databases review StarTeam Install.pdf

Re-authored by Ja"Mille Wilborn

Old KB# 28331
Comment List