KnowledgeBase Archive

An Archive of Early Microsoft KnowledgeBase Articles

View on GitHub

Q228927: FIX: Integration Slow Update w/Source Code Control Status

Article: Q228927
Product(s): Microsoft SourceSafe
Version(s): 1.1,4.0,4.1,4.2,5.0,6.0,97
Operating System(s): 
Keyword(s): kbinterop kbAccess97 kbSSafe400bug kbSSafe500bug kbSSafe600fix kbVBp400 kbVBp500 kbVBp6
Last Modified: 09-JUL-2002

-------------------------------------------------------------------------------
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 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:

  Q258648 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:

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

  Q258649 HOWTO: Tell That Visual Studio 6.0 Service Pack 4 Is Installed

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.

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 kbVS600sp4fix 
Technology        : kbVCsearch kbVC400 kbVSsearch kbVJsearch kbVFPsearch kbVBSearch kbSSafeSearch kbAudDeveloper kbAccessSearch kbZNotKeyword6 kbAccess97 kbZNotKeyword2 kbVB500Search kbVB600Search kbVB500 kbVB600 kbAccess97Search kbVB400Search kbVB400 kbVC410 kbVC420 kbVC500 kbVC600 kbVC32bitSearch kbVFP500 kbVFP600 kbVJ110 kbVJ600 kbSSafe600 kbSSafe400 kbSSafe500 kbSSafe32bitSearch kbVS97 kbVS600 kbVS97Search kbVS600Search kbVC500Search
Version           : :1.1,4.0,4.1,4.2,5.0,6.0,97
Issue type        : kbbug
Solution Type     : kbfix

=============================================================================

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.