Grant Fritchey (2/9/2011)

---

If you know which procedure is causing problems, get that query's plan handle and use DBCC FREEPROCCACHE(plan_handle). That way you're not nuking the cache, but going for surgical...

You're looking for the MERGE statement, I guess.

EDIT: clicked the wrong button.

EDIT: duplicate post

free_mascot (2/8/2011)

---

If you are have decided to go with flushed the proc cache; make sure you flushed the correct and specific cache which is problamatic (as per your investigation). And...

This issue might be similar to something I'm experiencing on a database of mine.

I'm adding the link to that topic, in case something interesting comes up:

http://www.sqlservercentral.com/Forums/Topic1060705-146-1.aspx

Grant Fritchey (2/8/2011)

Hey, while I've got you guys here, when I was off the network, the Virtual Box and the laptop stopped communicating. I'm sure I've got a configuration wrong....

Grant Fritchey (2/7/2011)

---

VirtualPC and VirtualBox. Loath as I am to admit it, the Oracle product is...

Did you compare the execution plans? Did you spot any difference?

If so, can you post:

1) Table scripts

2) Index scripts

3) Estimated data volumes (for each table)

4) Actual execution plans

This article[/url] is...

VirtualBox. Simply GREAT.

Then you would see 'ALTER INDEX ...' as command in the tempdb usage query.

Ok, so looks like you filled your tempdb with internal objects.

Can you post the execution plan? It should be included in the query I suggested.

Try running the script I suggested while your sql is running. It should display the tempdb usage.

If the tempdb usage is high, you will have to inspect the query plan...

I think you should do such a transformation on the app side, not on the database side.

That said, you could achieve it with some dynamic sql:

IF OBJECT_ID('tempdb..#Index') IS NOT NULL...

Don't cross-post, please.

http://www.sqlservercentral.com/Forums/Topic1059463-360-1.aspx

When tempdb runs out of disk space, you have to discover what filled the disk:

1) Tempdb itself. It could have been filled by temporary tables or internal objects.

2) Some other...