FIX: VSS Integration Slow Updating Source Code Control Status (228927)


The information in this article applies to:

  • Microsoft Visual SourceSafe, 32-bit, for Windows 4.0
  • Microsoft Visual SourceSafe, 32-bit, for Windows 5.0
  • Microsoft Visual SourceSafe, 32-bit, for Windows 6.0
  • Microsoft Visual C++, 32-bit Editions 4.0
  • Microsoft Visual C++, 32-bit Editions 4.1
  • Microsoft Visual C++, 32-bit Editions 4.2
  • Microsoft Visual C++, 32-bit Editions 5.0
  • Microsoft Visual C++, 32-bit Editions 6.0
  • Microsoft Visual Basic Professional Edition for Windows 4.0
  • Microsoft Visual Basic Professional Edition for Windows 5.0
  • Microsoft Visual Basic Professional Edition for Windows 6.0
  • Microsoft Visual FoxPro for Windows 5.0
  • Microsoft Visual FoxPro for Windows 6.0
  • Microsoft Visual J++ 1.1
  • Microsoft Visual J++ 6.0
  • Microsoft Visual Studio, Enterprise Edition 6.0
  • Microsoft Visual Studio 97
  • Microsoft Access 97
This article was previously published under Q228927

SYMPTOMS

When you use Visual SourceSafe integration with Visual C++, you may experience significant performance loss under the following conditions:
  • Two or more users execute a source control operation that results in refreshing the file status at the same time.
  • And, the project contains a high percentage of deleted files in the Visual SourceSafe project.
  • And, the project is more than one project away from the root project.
Performance loss can occur in other applications, such as Visual Basic, Visual FoxPro, Visual J++, Visual Studio, Visual Modeler, and Microsoft Access when using integration with Visual SourceSafe.

CAUSE

The performance problem is a result of the inefficient file access behavior in Visual SourceSafe.

RESOLUTION

This feature is available in the latest service pack for Visual Studio 6.0. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

258648 INFO: Visual Studio 6.0 Service Pack 4, What, Where, Why

STATUS

Microsoft has confirmed that this is a bug in the Microsoft products that are listed at the beginning of this article. This bug was corrected in Visual Studio 6.0 Service Pack 4. For more information about Visual Studio service packs, please click on the article numbers below to view the articles in the Microsoft Knowledge Base:

258648 INFO: Visual Studio 6.0 Service Pack 4, What, Where, Why

MORE INFORMATION

Steps to Reproduce the Behavior

Configuration

NOTE: At least three computers must be set up to reproduce this problem.

  • Computer 1: This is the server computer; it requires Windows NT 4.0, Visual SourceSafe Server Installation (this is the Visual SourceSafe database).
  • Computer 2: This is the client 1 computer; it requires Visual SourceSafe client, Visual C++ or one of the other applications listed in the "Symptoms" section.
  • Computer 3: This is the client 2 computer; requires Visual SourceSafe client and Visual C++ or one of the other applications listed in the "Symptoms" section.

Conditions

  • The directory in Visual SourceSafe must have a large number of deleted files.
  • The project is more than one project away from the root project.
  • The server computer must have Windows NT 4.0 installed.
  • The client computers must retrieve the same Visual SourceSafe project through the Integrated Development Environment (IDE) simultaneously.
If these four conditions are met, then the amount of time needed for Visual SourceSafe to update the files within the Visual C++ IDE is greatly increased. The further away the Visual SourceSafe project is from the root project and the more deleted files it has, the worse the problem gets. The worst-case performance loss occurs when the two client machines are of equivalent speed; for example, two P200s or two P233s.
Modification Type:MajorLast Reviewed:9/13/2006
Keywords:kbHotfixServer kbQFE kbBug kbfix kbinterop kbSSafe600fix kbVMod kbVS600sp4fix KB228927 kbAudDeveloper
©2004 Microsoft Corporation. All rights reserved.