Post reply

SQL Time Outs

  • February 4, 2008 at 12:02 am

    #121917

    Hi Everybody,

    I am new to adminstration side of SQL, and interested to know some ways to find out SQL time outs of applications. Any tools that might come handy in digging out SQL time outs. Currently I am using SQL server 2005.

    Thanks a lot.

  • February 4, 2008 at 9:22 am

    #774788

    Try using SQL profiler.

    You can specify the application name as one of the filters.

    Fair warning though if your timeouts aren't reproducible or regular you may have to collect a fair amount of data before getting the information you want.

    Kenneth

    Kenneth FisherI was once offered a wizards hat but it got in the way of my dunce cap.--------------------------------------------------------------------------------For better, quicker answers on T-SQL questions, click on the following... http://www.sqlservercentral.com/articles/Best+Practices/61537/[/url]For better answers on performance questions, click on the following... http://www.sqlservercentral.com/articles/SQLServerCentral/66909/[/url]Link to my Blog Post --> www.SQLStudies.com[/url]

  • February 4, 2008 at 9:32 am

    #774796

    Y, I agree. You might be able to use another type of monitoring tool, but profiler will prob get you what you need.

    Watch my free SQL Server Tutorials at:
    http://MidnightDBA.com
    Blog Author of:
    DBA Rant – http://www.MidnightDBA.com/DBARant

    Minion Maintenance is FREE:

  • February 4, 2008 at 10:07 am

    #774813

    I wish I knew of something... I had timeout issues all weekend. I thought it might have something to do with Tempdb trying to grow. Or some other database trying to autogrow. I changed the default size for tempdb... (didn't work) Unfortunately I have to agree Profiler is really going to be the only way.

    -WM

  • February 4, 2008 at 10:26 am

    #774827

    Now there is one really neat kind of trace that I found called a TRACE_PRODUCE_BLACKBOX. It basically does a rolling 5mb trace file. If you tried a regular trace and maxed it at 5 mb you could get an idea of how long that is for your trace. If its long enough .. say 12 hours or so (would probably have to be a fairly small trace) you may be able to use this and just kill it as soon as you hear about a timeout.

    That way you don't have to worry about using up all of your disk space on running a trace for timeouts that only occur every now and again.

    Williamminor,

    Have you thought about checking for network issues over the weekend? Assuming that your timeouts were unusual (the same code runs ok normally) then if there was a network slowdown of some type that could cause your problem.

    As a general case here we are using something called SQL Diagnostic Manager by Idera and that keeps a history of what's going on with the DB and the server that you can check back later.

    But that also costs money and profiler comes with SQL 🙂

    Kenneth

    Kenneth FisherI was once offered a wizards hat but it got in the way of my dunce cap.--------------------------------------------------------------------------------For better, quicker answers on T-SQL questions, click on the following... http://www.sqlservercentral.com/articles/Best+Practices/61537/[/url]For better answers on performance questions, click on the following... http://www.sqlservercentral.com/articles/SQLServerCentral/66909/[/url]Link to my Blog Post --> www.SQLStudies.com[/url]

  • February 4, 2008 at 11:23 pm

    #774988

    Thanks for your reply, but actually I was trying to find out a quick solution to find out SQL timouts without having to run profiler, like checking logs.

    can application server tell anything about SQL timeouts?

    Thanks in advance

Viewing 6 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic. Login to reply