The title of your thread caught my eye because I had a similar problem with SQL Server Agent across remote servers just recently.
Here is the question and solution I posted:
http://www.sqlservercentral.com/Forums/Topic1455796-391-1.aspx
I never did find a clean solution although I did get it working.
I'm hoping that if you or someone else finds a solution to your problem it might help me to make my solution better.
My thought question: Have you ever been told that your query runs too fast?
My advice:
INDEXing a poor-performing query is like putting sugar on cat food. Yeah, it probably tastes better but are you sure you want to eat it?
The path of least resistance can be a slippery slope. Take care that fixing your fixes of fixes doesn't snowball and end up costing you more than fixing the root cause would have in the first place.
Need to UNPIVOT? Why not CROSS APPLY VALUES instead?[/url]
Since random numbers are too important to be left to chance, let's generate some![/url]
Learn to understand recursive CTEs by example.[/url]
[url url=http://www.sqlservercentral.com/articles/St