Setting database analyze and repair options

You can specify the types of issues to check for and repair when analyzing databases.

1. Choose Tools > Administration > Analyze/Repair Database.

The Analyze Database dialog box opens.

2. Click Options.

The Analyze and Repair Options dialog box opens.

3. Select Perform CHECKDB (SQL Server only) to verify the integrity of database objects in SQL Server.

This option runs the SQL Server CHECKDB command when analyzing databases and returns a list of errors found. A DBA must manually repair the issues. Refer to the SQL Server help for information.

4. Select any Analyze and Repair options to check for specific repairable issues. See Repairs for common database issues for information about the repair actions performed when these issues are found.

Option	Checks for:
Check for share corruption	Shares that were not removed when a repository was removed, files still marked as base share files after shares were removed, and invalid shares of share links.
Check for duplicate filename conflicts	Duplicate filenames in the same repository.
Check for orphaned check outs	Files checked out by deleted users.
Check for missing check out computer	Checked out files missing a check out computer name.
Check for orphaned changelists	Pending changelists created by deleted users.
Check for undestroyed repositories	Undestroyed child repositories with destroyed parent repositories or undestroyed repositories in destroyed branches.
Check for inconsistent current versions	Files with inconsistent current version numbers.
Check for invalid tip versions	Files with invalid tip version numbers.
Check for undestroyed merge events	Merge event records that were not destroyed when the associated file was destroyed.
Check for branches with duplicate root repositories	Corrupted branches with duplicate or invalid root repositories after a template was applied.
Check for orphaned filters	Filters with deleted users as the owners.
Check for mismarked revision records	File revision records that were incorrectly marked as destroyed.
Check if VACUUM is needed	PostgreSQL vacuum needed to remove dead table rows to free up database space and improve performance. PostgreSQL only.

Click Select All to select all options or click Select None to clear any selected options.

5. Select Force reindex to reindex database tables.

You may want to reindex tables if you notice a performance slowdown. This option only applies to PostgreSQL and SQL Server databases.

Reindexing may temporarily affect Surround SCM performance. As with any repair, you may want to consider reindexing only during off-peak hours.

6. Click OK to save the changes.