FIX: VSS Integration Slow Updating Source Code Control Status

ID: Q228927

The information in this article applies to:
  • Microsoft Visual SourceSafe, 32-bit, for Windows versions 4.0, 5.0, 6.0
  • Microsoft Visual C++, 32-bit Editions, versions 4.0, 4.1, 4.2, 5.0, 6.0
  • Microsoft Visual Basic Professional Edition for Windows, versions 4.0, 5.0, 6.0
  • Microsoft Visual FoxPro for Windows, versions 5.0, 6.0
  • Microsoft Visual J++, versions 1.1, 6.0
  • Microsoft Visual Studio versions 6.0, 97
  • Microsoft Access 97

SYMPTOMS

When using Visual SourceSafe integration with Visual C++, you may experience significant performance loss when:

  • 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 bug was corrected in a hotfix for Microsoft Visual SourceSafe 6.0.


STATUS

Microsoft has confirmed this to be a problem in the Microsoft products listed at the beginning of this article.

This bug was corrected in a hotfix for Visual SourceSafe 6.0.


MORE INFORMATION

Steps to Reproduce Behavior

Configuration

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

  • Machine 1: This is the server machine; requires Windows NT 4.0, Visual SourceSafe Server Installation (this is the SourceSafe database).


  • Machine 2: This is the client 1 machine; requires Visual SourceSafe client and Visual C++ or one of the other applications above.


  • Machine 3: This is the client 2 machine; requires Visual SourceSafe client and Visual C++ or one of the other applications above.


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 machine must have Windows NT 4.0.


  • The client machines must retrieve the same SourceSafe project through the 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 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.


REFERENCES

For more information about eligibility for no-charge technical support, please see the following article in the Microsoft Knowledge Base:

Q154871 Determining If You Are Eligible for No-Charge Technical Support

Additional query words: Visual SourceSafe integration inefficient file access performance slowdown

Keywords : kbinterop kbAccess97 kbSSafe400bug kbSSafe500bug kbSSafe600fix kbVBp400 kbVBp500 kbVBp600 kbVC400 kbVC500 kbVC600 kbVFp500 kbVFp600 kbVJ110 kbVJ600 kbVMod kbVS97 kbVS600 kbSSafe600qfe kbSSafe500qfe
Version : WINDOWS:1.1,4.0,5.0,6.0,97; winnt:4.0,4.1,4.2,5.0,6.0
Platform : WINDOWS winnt
Issue type : kbbug


Last Reviewed: December 2, 1999
© 2000 Microsoft Corporation. All rights reserved. Terms of Use.