Microsoft KB Archive/179150

= BUG: DBCC SQLPERF(logspace) Returns Incorrect Database Name =

Article ID: 179150

Article Last Modified on 10/16/2003

-

APPLIES TO


 * Microsoft SQL Server 6.0 Standard Edition
 * Microsoft SQL Server 6.5 Standard Edition

-



This article was previously published under Q179150



BUG #: 17704 (6.5) 15730 (6.0)



SYMPTOMS
After dropping a database and then creating another database with a shorter name, DBCC SQLPERF(logspace) returns an incorrect name for the newly created database.



WORKAROUND
To work around this problem, make sure the open databases parameter is set high enough and then stop and restart SQL Server. After doing this, DBCC SQLPERF will display the correct database name.



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



MORE INFORMATION
DBCC SQLPERF(logspace) shows the new database name overwriting the dropped database name without cleaning up the rest of the characters of the dropped database name.

The following is an example on how to reproduce the problem:

use master go  create database cus_data   -- creates database 'cus_data' on default device go  dbcc sqlperf(logspace)     -- shows 'cus_data' as the database name go

drop database cus_data    -- drops current database go  create database xyz        -- creates database 'xyz' go  dbcc sqlperf(logspace)     -- shows 'xyz_data' as the database name -- instead of 'xyz' go

drop database xyz         -- reclaim space on default device go

The incorrect database name will also appear in the SQLServer-Log object's instance within the Performance Monitor.

Additional query words: transaction log db

Keywords: kbbug KB179150

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.