FIX: When You Edit Stored Procedures Under Source Control, Spaces Are Removed

This article has been archived. It is offered "as is" and will no longer be updated.
When you check in stored procedures to Visual SourceSafe, the spaces are removed. This makes the Visual SourceSafe copy different from the SQL Server copy. This problem can cause build failures when you retrieve the stored procedures from Visual SourceSafe by using Get latest version, and then script them for build on a different computer running SQL Server.
A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Visual Studio 6.0 service pack that contains this hotfix.

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 about support costs, visit the following Microsoft Web site:Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

The English version of this fix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
   Date         Time   Version     Size     File name   -----------------------------------------------------   21-Feb-2003  22:18  408,848  Mdt2dbns.dll

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.

Article ID: 815236 - Last Review: 02/27/2014 21:17:36 - Revision: 1.5

Microsoft Visual Studio 6.0 Service Pack 5, Microsoft Visual SourceSafe 6.0C

  • kbnosurvey kbarchive kbhotfixserver kbqfe kbfix kbbug KB815236