|
Home > Archive > MS SQL Server > September 2005 > I Hate Timeouts !
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
|
|
| Jim Trowbridge 2005-09-19, 3:23 am |
| Everything travelling real smooth, then kersplat !
We have a load balanced node pair running a single application, both nodes
connected to the single database server, both lost connectivity to the
database, one recovered, the other dropped its bundle big time.
Naturally, everyone wants to know why and how to stop it happening again !
The only SQL job I found running at the time is a transaction log backup -
runs every 15 minutes, took 3 seconds. How can this be so disastrous ?
Anyone got any clues where to start looking ?
Or even any general advice on timeouts and how to crunch them ?
| |
| Mike Epprecht \(SQL MVP\) 2005-09-19, 7:23 am |
| Hi
What does the SQL Server Event Log say?
If nothing is reported there, what about the network and your DNS or your
domain controllers? Can you exclude them from causing the problem?
You don't loose connectivity for no reason. Something happened. Does your
application server log errors so that you can figure out what happened?
Regards
--------------------------------
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Jim Trowbridge" < JimTrowbridge@discus
sions.microsoft.com> wrote in message
news:3B13A986-7A4E-4940-9A1D- 874017B8BAD5@microso
ft.com...
> Everything travelling real smooth, then kersplat !
>
> We have a load balanced node pair running a single application, both nodes
> connected to the single database server, both lost connectivity to the
> database, one recovered, the other dropped its bundle big time.
>
> Naturally, everyone wants to know why and how to stop it happening again !
>
> The only SQL job I found running at the time is a transaction log backup -
> runs every 15 minutes, took 3 seconds. How can this be so disastrous ?
>
> Anyone got any clues where to start looking ?
> Or even any general advice on timeouts and how to crunch them ?
|
|
|
|
|