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

• Microsoft SQL Server, versions 6.0 and 6.5

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

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

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

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

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