That feeling when you've got a Linked Server connection to a remote site who thought they had everything set up and you just needed to get your end set up, but they didn't have everything set up right so now your end works and theirs doesn't and the people who require the data from the remote site are calling you...
:crazy::sick:
Sorry man, I feel for you when dealing with linked servers. My problem tends to be somehow the network admins keep managing to screw up Kerberos and delegation so linked servers that used to work stop working and of course it's a database problem.
You know, I'd almost trade you problems...
Mine is SQL connecting to a remote Oracle server, over a WAN link that sometimes decides to crap out half-way through a data pull, or while SQL is waiting on the Oracle to start sending data, leaving a stuck connection that won't die and can't be killed...
But when the customer gets to me about it, and I test it, it's working fine again...
Hey - I've had that problem. The WAN doesn't die frequently, but when it does, it's a disaster. My usual problem is that the query takes forever to run on the Oracle server.
It's especially annoying because it fails silently, just leaving a running / idle query behind. In my customers' case, it's kind of worse because while if we were doing nightly data pulls, something could be set to check at a set time "did the data arrive," and if not, run again. But nooo, they *require* near real-time data, which means at random points through out the day, they're going out through the link to get their data.
:unsure: