"Give me clarity over cute/compact/tricky code any day !"

How about you give us your definitions??

Basic answer.  Overwritten file + new file in use = you better have another copy.  Sorry but there's nothing anyone can do on this one.

P.S.  Another solution would be to ask for the opinion of the community on your situation.  Maybe that would give even more punch than the said article.   If you go...

Maybe if you could provide even more details, it would give us a better idea.  That consultant story doesn't ring any bells at the moment.

Good luck finding the article.

That'll give you the answer you need recreate your proc with the code you just posted and see the result for yourself .

Select Text...

http://www.sqlservercentral.com/columnists/dpeterson/lookuptablemadness.asp

Was it about a single lookup table?  A thread with a massive amount of responses?

Slightly different version but your version should work.

If it doesn't then you need to post the full sp code.

CREATE TABLE dbo.A

(b INT NOT NULL)

GO

SELECT * FROM dbo.a

 

If it works in QA, it'll work in the proc.. How are the codes different?

May I ask why the date is not the clustered index on the table?

Does the server have permission to delete that file?

I don't think you need to be there to check on the jobs.  If it makes you feel any better, then you can simulate the scenario by changing the time...

Check the final selects, doesn't get much simpler than that :

Select * from dbo.Mytable where Colid IN (Select CAST(EachID as <colid datatype&gt AS EachID,...

The server won't timeout on its own.  Are you sure it's not the connection or object command that times out??  or the web server if asp(X) code?

Yeah that's some kind of session timeout.  They know about it but can,t resolve at the moment.  Make sure you backup your message before hitting send