It's by design and for good reasons... search the articles on this forum for best practices + fully qualified object names + cached plans.  You'll surely find the missing link in...

Most of the time.

But you can have more than 1 plan per procedure / object / query.  That's why as a long shot I proposed the recompile.  A more drastic...

Changing the sp recompiled it, or more to the point changed the current execution plan.  So that threw out any possible bad plan out the window and more importantly out...

No idea what the problem is.... can't wait to see what everyone else can come up with!

Ya that's the solution he can't make work from the link... Got any working sample you an provide?

You don't need to output the sort column to use it in the order by :

CREATE TABLE tblContent (content varchar(2))

INSERT INTO tblContent (content) VALUES ('1a')

INSERT INTO tblContent (content) VALUES...

Tried the same openrowset/openquery (the one which doesn't required a live linked server)?

That'll work.

CREATE TABLE tblContent (content varchar(2))

INSERT INTO tblContent (content) VALUES ('a')

INSERT INTO tblContent (content) VALUES ('c')

INSERT INTO tblContent (content) VALUES ('b')

INSERT INTO tblContent (content) VALUES ('e')

INSERT INTO tblContent (content) VALUES...

I didn't look at the link but here's how I do it :

EXEC [LinkedServerName].msdb.dbo.sp_start_job @job_name = 'UpdateDeveloppementDatabase - Documentation'

If tat doesn't work can you specify the errors you...

I was thinking that proc a runs fines.

Proc b calls proc a.

Either plan b can be screwed, or plan b calls for an older/different version of plan a.

That's why recompile...

Recompile did nothing?

A few more ideas came to mind... maybe that'll spark a light for you.

Does tempdb have to grow while doing that process?

Any other log or data file need to grow?

What's...

Tried recompiling the objects?

How many indexes on the inserted table?

Is there a trigger on that table [now].

Ya like select the data you want to keep then drop that table...  but I'm sure you knew about that one .

You can delete directly in the system tables in 2005 ?!?!