Evil Kraig F (1/12/2012)
This is more a linked server than a job issue. The proc itself won't error, so the job is clueless there was a problem.
When you put it that way, it actually makes sense what's going on. Thank you for that translation.
So, I wonder if this is a linked server "bug" or if it's deliberate behavior with an unintended side effect.
My linked server uses the SQL Server Native Client 10.0 provider, is set up using a specific security context (the last option), and has Query Timeout set to 0 (which I thought was no timeout). The other options are listed below.
Collation Compatible: False
Data Access: True
RPC: True
RPC Out: True
Use Remote Collation: True
Collation Name: <blank>
Connection Timeout: 0
Distributor: False
Publisher: False
Subscriber: False
Lazy Schema Validation: False
Enable Promotion of Distributed Transactions: True