BUG: Multiple Temp Table Drops May Cause Timeslice and Trap D

  - Microsoft SQL Server version 4.2 for OS/2

SYMPTOMS

Executing a Transact-SQL command batch that attempts to drop three or more temp tables will cause a timeslice error followed by a trap D of the server under the following conditions:

• Only one of the temp tables dropped in the batch can exist.
• The non-existent tables dropped in the batch must be dropped in succession.

   timeslice -1501, current process infected.

WORKAROUND

The error can be avoided if the DROP TABLE statements are divided into separate batches. This is demonstrated as follows:

   select uid into #mytemp from sysusages
   go
   drop table #mytemp
   go
   drop table #mytemp2  /* does not exist */
   go
   drop table #mytemp3  /* does not exist */
   go
   select uid into #mytemp from sysuages

STATUS

Microsoft has confirmed this to be a problem in SQL Server version 4.2 for OS/2. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.

MORE INFORMATION

Steps to Reproduce the Problem

Executing the following query will demonstrate this problem. The table #mytemp1 is the temp table that exists. The tables #mytemp2 and #mytemp3 do not exist.

   select uid into #mytemp from sysusages
   go
   drop table #mytemp
   drop table #mytemp2  /* does not exist */
   drop table #mytemp3  /* does not exist */
   go
   select uid into #mytemp from sysuages