Private Temp Table being accessed by different spids - huh?

• vest

  Newbie

  Points: 7

  More actions

  April 1, 2004 at 11:28 am

  #108109

  Any insight anyone has on this would be appreciated.  Here's the situation:

  spid 55 executes a stored proceure that creates a standard, private temp table

  spid 74 executes the same stored procedure

  spid 74 gets blocked by 55 because it's trying to create the same objectid that 55 created.

  But it's a private temp table!  I don't understand why one spid is trying to access a temp table created by a different spid!

  More info...  Here's how the temp table gets created and populated:

  create table #Global_Holdings (Portfolio varchar(10)) -- create stub table

  exec spLibAltGlobalHoldings    -- add columns to stub table

  insert into #Global_Holdings

   exec spRptGlobalDailyHoldings @AsOfDate='1/1/2004'

  The spLibAltGlobalHoldings is simply an alter table statement that adds columns.  We have been using this construct for a very long time without problems so I don't think this is the culprit, but I'm not ruling anything out.

  The screen shot shows the evidence that two spids are trying to access the same private temp table.

  Help!

  

• Steve Jones - SSC Editor

  SSC Guru

  Points: 740641

  More actions

  April 1, 2004 at 11:39 am

  #501501

  If this actually occurs, it's a bug. Call PSS.