Panic over

[bellinghman]

Before leaving for Covent Garden yesterday, I was attempting remote diagnosis on a software setup in Prague. Still not fixed by the time I left, but my colleague over there had gone to voice mail, so off to London to see purple_terror, and simonb and lusercop among others.

This morning I get a message left on my voice mail at 07:15 to say "It's all OK, it's sorted, it was the customer having two SQL Servers, and one part of the system was looking at the wrong server."

Argh!

At least the problem has gone.

Comments

[liasbluestone.livejournal.com]

Life would be a lot simpler without customers, would it not.

That reminds me of the problem I had to sort a few months ago, where it turned out that the customer had an extra server on the network, which was running a different version of the software to all the others.

[burkesworks.livejournal.com]

At least the problem has gone.

I suppose that's one way of looking at today's news, though seeing the insubstantial careerist on News 24 as I type gives the lie to that :)

[erikvolson.livejournal.com]

The best SQL server bit I saw.

Me: "What does this stored procedure do?"

Developer: "It uses a linked server to call an SP on the other SQL server."

M: "Okay, now tell me what that stored procedure does."

D: "Well, it, uhh, uses a linked server to call a SP here."

M: "We need to do what now?"

D: "Fix that?"

M: "I would have also accepted "drink heavily""

[bellinghman.livejournal.com]

Uhhuh.

It's amazing how such things can end up in your code, purely as a result of layering.