Perhaps, but I often don't overreact on the first occurrence. I think there are many one time events, and it isn't necessarily worth chasing them all down.

Certainly it's a...

Gary Varga (2/11/2015)

---

One key issue that kept cropping up in my mind when reading this thread was that there was a lot of assuming that there is a single application...

54F as a high yesterday for me, today the high is 50F, woke up to a light dusting, about an inch, of snow. Had to scrape the car to take...

Supposed to be 50s the next week. Getting warmer in the mountains as well, which sucks. Supposed to ski this weekend.

Sunny and 45F in Denver 😀

That suggests to me that it's security somehow. The linked server can be set to use multiple security contexts, different than you in SSMS or SQL Agent. I'd look there.

No rush. Please tackle it if you'd like.

Use one of these scripts: http://www.sqlservercentral.com/search/?q=bcp+all+out&t=s&sort=relevance

BCP is the fastest way. I have a script up there to export all tables. There are corresponding scripts to pull all the data in.

Ouch. I'm probably 0-4 then, US American, rooting for the Cowboys, Yankees, and Lakers since I...

Grant Fritchey (2/4/2015)

---

Nah, I hear he's a giant bag of wind and a bit...

You could implement your own SQLCLR function from the .NET namespace to handle larger values.

Could be parameter sniffing, perhaps a plan flush that compiled poorly the next time, it's not the index itself.

Are you calling the linked server the same way directly and through the SP? Meaning same security context? Check the SP doesn't have any execute AS.

Linked servers get tricky because...

It's in the registry, IIRC. However, if there are overriding parameters in the services applet or however the service is started, they should take effect.

If you restarted, I can't imagine...

You always have scheduled tasks, so SQL Agent, while nice, isn't necessary for many things.