When you use Visual SourceSafe integration with Visual C++,
you may experience significant performance loss under the following
- 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
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.
The performance problem is a result of the inefficient file
access behavior in Visual SourceSafe.
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
List of bugs that are fixed in Visual Studio 6.0 Service Pack 6
Steps to Reproduce the Behavior
: At least three computers must be set up to reproduce this
- Computer 1: This is the server computer; it requires
Windows NT 4.0, Visual SourceSafe Server Installation (this is the Visual
- 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
- The directory in Visual SourceSafe must have a large number
of deleted files.
- The project is more than one project away from the root
- The server computer must have Windows NT 4.0
- The client computers must retrieve the same Visual
SourceSafe project through the Integrated Development Environment (IDE)
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.
Article ID: 228927 - Last Review: February 28, 2014 - Revision: 4.4
- Microsoft Visual SourceSafe 4.0 Standard Edition
- Microsoft Visual SourceSafe 5.0 Standard Edition
- Microsoft Visual SourceSafe 6.0 Standard Edition
- Microsoft Visual C++ 4.0 Standard Edition
- Microsoft Visual C++ 4.1 Subscription
- Microsoft Visual C++ 4.2 Professional Edition
- Microsoft Visual C++ 5.0 Standard Edition
- Microsoft Visual C++ 6.0 Service Pack 5
- Microsoft Visual Basic 4.0 Professional Edition
- Microsoft Visual Basic 5.0 Professional Edition
- Microsoft Visual Basic 6.0 Professional Edition
- Microsoft Visual FoxPro 5.0 Standard Edition
- Microsoft Visual FoxPro 6.0 Professional Edition
- Microsoft Visual J++ 1.1 Standard Edition
- Microsoft Visual J++ 6.0 Standard Edition
- Microsoft Visual Studio 6.0 Enterprise Edition
- Microsoft Visual Studio 97 Service Pack 3
- Microsoft Access 97 Standard Edition
|kbnosurvey kbarchive kbhotfixserver kbqfe kbbug kbfix kbinterop kbssafe600fix kbvmod kbvs600sp4fix KB228927|