KnowledgeBase Archive

An Archive of Early Microsoft KnowledgeBase Articles

View on GitHub

Q155880: DOC: README FIRST Card Has a Typo in Stored Procedure Name

Article: Q155880
Product(s): Microsoft C Compiler
Version(s): 4.2
Operating System(s): 
Keyword(s): kbusage kbdocerr kbEEdition kbVC
Last Modified: 04-AUG-2001

-------------------------------------------------------------------------------
The information in this article applies to:

- Microsoft Visual C++, version 4.2 
-------------------------------------------------------------------------------

SUMMARY
=======

The README FIRST Card has a typo in the installation procedures for the SQL
Debugging Components. The README FIRST Card identifies the stored procedure as
sp_sdidedebug. The correct stored procedure name is sp_sdidebug.

MORE INFORMATION
================

The section "Installing SQL Debugging Components" in the README FIRST Card has
the following information in step 7:

  7. Grant execute privileges on the extended stored procedure sp_sdidedebug to
  enable SQL debugging on your Microsoft SQL Server.

NOTE: This error has also been documented in the MSDEV\EEREADME.WRI file.

The correct stored procedure name is sp_sdidebug.

Additional query words: kbVC420bug

======================================================================
Keywords          : kbusage kbdocerr kbEEdition kbVC 
Technology        : kbVCsearch kbAudDeveloper kbVC420
Version           : :4.2

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

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.