Maybe the query was running off another DB and was growing tempdb and another db like crazy... just another option.

600 mb is not too hard to believe... but 600gb, now that's out there, especially for a single query on a test server?!?!?!

What query have you tried so far, what result did it get you and what is wrong with it?

600 GB large???????????

I just edited my previous answer with more details.

Good luck.

Hell yeah!

You need to consider what queries are running. If they are using the guid as the main filter : Select * from Whatever Where guid = 'dfkjsd'....... and...

I already answered...

You forgot to tell that it's SUMMER down there :P.

They shouldn't, unless manually deleted.

But they could be part of some undelete trash can.

Am I reading right, 617 GB???

Assuming the drop succeeded, that might be some windows error.

Have you tried rebooting the server?

What was the size of those files?

Check if windows didn't grow the paging file.

Also temp files might have gobbed it back up.

There are 12s of explanations, especially on the system...

Yup been there, done that. Don't put the clustered index on the GUID, ever.

All those variables are empty... null is the only thing that can come out of this.

What exactly do you need to do? There's no need for a function here...

Jack Corbett (1/7/2009)

---

Michael Earl (1/7/2009)

---

I moved out of there years ago - that entire section of the country is creepy.

Now I'm in CT - we only burn cars at Dave...

And btw, most servers can handle 50K insert in less than 1 sec. So in a day will not be an issue, ever.