Microsoft KB Archive/171944

= BUG: DBCC OPENTRAN Reports Incorrect Database Name =

Article ID: 171944

Article Last Modified on 10/3/2003

-

APPLIES TO


 * Microsoft SQL Server 6.5 Standard Edition

-



This article was previously published under Q171944



BUG #: 17016 (WINDOWS: 6.5)



SYMPTOMS
If you execute DBCC OPENTRAN against a database, the first line, which identifies the name of the database, reports an incorrect database name. However, the results show the correct open transaction information for the database specified in the DBCC statement.



CAUSE
The sp_renamedb procedure had previously been used to rename the database.



STATUS
Microsoft has confirmed this to be a problem in Microsoft 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.



MORE INFORMATION
The name reported by DBCC OPENTRAN is the name of the database at the time it was created.

For example, if you run DBCC OPENTRAN(pubsdb), you will get the following results:

Transaction Information for database: pubs

Oldest active transaction:

       SPID          : 11 UID          : 1 SUID         : 1 Name         : user_transaction RID          : (1365, 7) Time Stamp   : 0001 0000A95F Start Time   : Jun 11 1997 10:35:57:086AM DBCC execution completed. If DBCC printed error messages, see your System Administrator.

Keywords: kbbug kbpending kbusage KB171944

-

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

© Microsoft Corporation. All rights reserved.