BUG: VSS Integration Slow Updating Source Code Control Status

• 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.

CAUSE

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

RESOLUTION

A supported fix for Visual SourceSafe 5.0 that corrects this problem is now available from Microsoft, but it has not been fully regression tested and should be applied only to systems experiencing this specific problem.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information on support costs, please go to the following address on the World Wide Web: http://support.microsoft.com/support/supportnet/default.asp

The English version of this fix should have the following file attributes or later:

Name	Size	Date	Time	Version#	Platform
Ssscc.dll	1,165KB	4/8/99	12:07 PM	05.00.8463	x86

NOTE: If this product was already installed on your computer when you purchased it from the Original Equipment Manufacturer (OEM) and you need this fix, please call the Pay Per Incident number listed on the above Web site. If you contact Microsoft to obtain this fix, a fee may be charged. This fee is refundable if it is determined that you only require the fix you requested. However, this fee is non-refundable if you request additional technical support, if your no-charge technical support period has expired, or if you are not eligible for standard no-charge technical support.

STATUS

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

MORE INFORMATION

Steps to Reproduce Behavior

Configuration

• 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.

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 kbSSafe600bug kbVBp400 kbVBp500 kbVBp600 kbVC400 kbVC500 kbVC600 kbVFp500 kbVFp600 kbVJ110 kbVJ600 kbVMod kbVS97 kbVS600 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: May 6, 1999