Dunno what happened there

[John Duncan]

Lost you for a minute there. Luckily I'm at work so did what I always do...waited a few minutes and it fixed itself.

I suspect a SQL Cluster Failover...

 

[JoelSim]

JohnDuncan:Lost you for a minute there. Luckily I'm at work so did what I always do...waited a few minutes and it fixed itself.I suspect a SQL Cluster Failover...

Me too. Couldn't be anything else really

 

[John Duncan]

JoelSim:
JohnDuncan:Lost you for a minute there. Luckily I'm at work so did what I always do...waited a few minutes and it fixed itself.I suspect a SQL Cluster Failover...

Me too. Couldn't be anything else really

Not with our cacheing strategy, no...

 

[JoelSim]

JohnDuncan:JoelSim:
JohnDuncan:Lost you for a minute there. Luckily I'm at work so did what I always do...waited a few minutes and it fixed itself.I suspect a SQL Cluster Failover...

Me too. Couldn't be anything else really

Not with our cacheing strategy, no...

I agree. Great cacheing strategy JD. Yes

 

[Alec]

indeed. positively first rate. ive always thunk it.

 

[Anonymous]

odd that it happened when the debates were raging on the god threads

the almighty isnt happy

 

[John Duncan]

one off:
odd that it happened when the debates were raging on the god threads

the almighty isnt happy

And lo, he smote the SQL Server and saw that it was good.

 

[plastic penguin]

JohnDuncan:Lost you for a minute there. Luckily I'm at work so did what I always do...waited a few minutes and it fixed itself. I suspect a SQL Cluster Failover...

Clearly working too hard, JD. You look rather pale.....