BUG: SQL-DMO ::GetMemUsage Method Returns Empty String

Last reviewed: April 16, 1997
Article ID: Q152621
The information in this article applies to:
  • Microsoft SQL Server, versions 6.0 and 6.5
BUG #: 15500 (6.00 6.50) (sqlserver)

SYMPTOMS

When you carry out the SQL-DMO database consistency check (DBCC) methods, you can receive empty return values. In most cases this is valid output.

All the SQL-DMO DBCC methods use the WITH NO_INFOMGS option to suppress information level output.

For example, if you use the ::CheckAllocations method and there are no problems, the output remains empty. However, if the processing encounters an error greater than Severity 10, it is placed in the output string.

    strOutput$ = oServer.Databases("pubs").CheckAllocations

CAUSE

In the case of ::GetMemUsage, all output is informational and is less than Severity 10, so it is always suppressed.

WORKAROUND

Run DBCC MemUsage from ISQL or ISQL/W.

STATUS

Microsoft has confirmed this to be a problem in Microsoft SQL Server versions 6.00 and 6.5. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.


Additional query words:
Keywords : kbbug6.00
Version : 6.0 6.5
Platform : WINDOWS


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 16, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.