BUG: DBCC MEMUSAGE Error

Last reviewed: April 28, 1997
Article ID: Q88496

The information in this article applies to:
  • Microsoft SQL Server version 4.2 for OS/2
BUG# OS/2: 1399 (4.2)

SYMPTOMS

Executing the command "DBCC MEMUSAGE" does not display the memory usage results, and returns only the message:

   DBCC execution completed. If DBCC printed error messages,
   see your System Administrator.

CAUSE

SQL Server incorrectly evaluates the DBCC MEMUSAGE command when it is issued in all uppercase characters. Issuing the DBCC MEMUSAGE command in all uppercase characters suppresses the memory-usage statistics. Other DBCC commands, such as CHECKALLOC, CHECKDB, CHECKCATALOG, and DBREPAIR all function correctly, regardless of whether they are issued in uppercase or lowercase characters.

WORKAROUND

To avoid this problem, always issue the DBCC MEMUSAGE command in lowercase characters ("dbcc memusage"). If the command has already been issued in all uppercase characters, issuing it in all lowercase characters returns the correct results. You can then issue the command in uppercase or lowercase characters, returning the proper results for the remainder of that user's connection.

STATUS

Microsoft has confirmed this to be a problem in SQL Server version 4.2 for OS/2. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.


Additional query words: Transact-SQL
Keywords : kbbug4.20 kbprg SSrvServer
Version : 4.2
Platform : OS/2
Issue type : kberrmsg


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.

Last reviewed: April 28, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.