BUG: Use <Database> Does Not Properly Change @@DBTS Context

 Last reviewed: April 9, 1997
Article ID: Q157518
The information in this article applies to:
  • Microsoft SQL Server, versions 6.0 and 6.5
BUG #: 15634 (WINDOWS 6.50)

SYMPTOMS

The Use <Database> statement does not change the context of the @@DBTS, unless the Use <Database> statement is run in a separate Transact-SQL batch.

WORKAROUND

To work around this problem place the Use <Database> statement in a separate batch.

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

The following query demonstrates the problem: 

   use pubs
   go

   select db_name(), @@DBTS
   go

   use tempdb
   select db_name(), @@DBTS
   go

   select db_name(), @@DBTS
   go
The following is the result of the query above: 

   ------------------------------ ------------------
   pubs                           0x0100000097180000

   **ERROR, database context is really tempdb but @@DBTS value belongs to
   PUBS

   ------------------------------ ------------------
   tempdb                         0x0100000097180000

   ------------------------------ ------------------
   tempdb                         0x010000003e1a0000

Additional query words:
Keywords : kbbug6.00 kbbug6.50 kbusage SSrvTran_SQL
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 9, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.