BUG: Edit Database Shows Incorrect Values w/Log Size Over 2 GB

Last reviewed: October 21, 1997
Article ID: Q175412

The information in this article applies to:

Microsoft SQL Server version 6.5

BUG #: 16781 (NT: 6.5)

SYMPTOMS

If a database is created with a log size of over 2 GB, the Edit Database dialog box in SQL Enterprise Manager may incorrectly report Log Size as zero.

WORKAROUND

To work around this problem, use the following query to return the log size in MB for the database:

   select (sum(size)/512) from master..sysusages
   where dbid = db_id('<database_name>') and segmap = 4

STATUS

Microsoft has confirmed this to be a problem in SQL Server version 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: SEM disk space free 0
Keywords : kbbug6.50 SSrvEntMan kbenv
Version : WINNT:6.5
Platform : WINDOWS
Issue type : kbbug
Solution Type : kbworkaround

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