1 - My name is Remi, my surname is carpal tunnel because I post too much .

2 - You shouldn't have to rebuild...

Nice to see you back online... been almost 2 days now .

What does this sp do?

Do you have more than one processor on that server (or hyper threading)?

Can we see what it looks like?? Haven't seen a real monster in some while .

Ya that's alway safer that way .

Not to mention that truncate won't delete only some of the rows anyways... now that would really be a big concern .

I thaught that you meant for the whole db/server .

New information that you might find usefull here :

http://www.sqlservercentral.com/forums/shwmessage.aspx?forumid=5&messageid=207156

Glab to be right for once .

Don't do that... stats HELP the server, they are not a bad thing in any way. You might suffer a performance drop for a few minutes while they are...

This is were the packages are kept... I don't know the best route to take from there. But here's one that seems safe...

Restore msdb to a new clean server....

Did you save the package to bas file?

Do you have a backup of msdb?

Yup, been bitten by this one once, never again .

We're probabely missing quite a few columns in that exemple .

This seems like the most evil idea... but it would work :

Select * into NewTable from Openrowset (linkedserverinfo, 'Exec procedure...')