Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
Lumbago
Norsk Yak Master
3271 Posts |
 Posted - 2004-06-21 : 09:34:07
|
| Hi people,one of my very good customers told me today that he is experiencing quite a few timeouts on our website. The webserver seems to be doing fine I find this odd becouse I haven't heared anything from my other customers but I still have to find out what's going on. How do I capture this? I have tried using profiler but I'm not too experienced with it...which filters would I use for example? Will Lock:Timeouts be the one I'm looking for...?--Lumbago"Real programmers don't document, if it was hard to write it should be hard to understand" |
|
|
derrickleggett
Pointy Haired Yak DBA
4184 Posts |
Posted - 2004-06-21 : 13:37:08
|
| Lock:Timeouts would be a good thing to profile for. You'll also probably want to profile anyting that runs over a couple seconds. Each one will need to be it's own profile as filters use AND logic instead of OR. Does he have the timeout messages that are occuring? It would help you pinpoint a slow running procedure. Also, have you checked the application log on the web server. They should be showing up there.MeanOldDBAderrickleggett@hotmail.comWhen life gives you a lemon, fire the DBA. |
 |
|
|
Lumbago
Norsk Yak Master
3271 Posts |
Posted - 2004-06-22 : 06:30:07
|
| Thanx derrick, but what do I do to only trap the timeouts in profiler? I haven't actually looked at the application log on the webserver for quite a while so I'll look into that to... |
|
|
|
derrickleggett
Pointy Haired Yak DBA
4184 Posts |
Posted - 2004-06-22 : 07:40:35
|
| Well, it depends how you have your application setup. If it's not setup for auto-rollback, you need to just look at long running queries....for example limit to anything that runs over 10 seconds. You could also add the events of Attention, EventLog, OLEDB, and Lock:Timout to see if that's causing you any problems. It's not fun troubleshooting these things sometimes. The application log is usually the easiest place if the application is set up correctly.MeanOldDBAderrickleggett@hotmail.comWhen life gives you a lemon, fire the DBA. |
|
|
|
|
|
|
Trapping timeouts