Lazy Spool - How can i improve/avoid this?

  • About 75 percent of cost is being used by "Table Spool(Lazy Spool)" in the execution plan. The inputs on this operator are from an clustered index scan(cost is 0%) and a index seek(cost is 0%) from the same table with actual rows return 0 for each. I did do some research on lazy spool and seems like it is creating a temp table on temp db but why is the cost 75% when 0 records are fed as inputs?

  • Check if you have appropriate indexes.

  • Query, table definitions, index definitions and execution plan please.

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass

Viewing 3 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic. Login to reply