It could be, as AS suggests, that upgrades are the culprit. If you had a session connected to one server and that server was taken off line for upgrade there would be a SQL glitch when it tried to route you to another server. COuld be to omany connections and you lose priority in the queue thus get a "no connection". OR...it could be reflective of how they are doing data replication across database servers but I have long since "moved to the business end of the building" on that one. I like Zhann's response though: "Pay no attention to the man behind the green curtain" :)