Post reply

OLEDB Wait Type.... why, and how to resolve?

  • January 15, 2007 at 1:15 pm

    #115687

    i'm getting about 591,442,039 waiting tasks for wait: OLEDB

    question is... where to begin? it's just OLEDB ??

    _________________________

  • January 16, 2007 at 7:17 am

    #683464

    any ideas would be greatly appreciated.

    thanks in advance.

    _________________________

  • January 16, 2007 at 1:10 pm

    #683595

    any linked sevrer?

  • January 16, 2007 at 2:11 pm

    #683610

    thanks for the reply...

    i don't see any thing as a linked server, but i see a bunch of providers.

    _________________________

  • January 16, 2007 at 2:21 pm

    #683617

    can you please check

    DBCC INPUTBUFFER(<SPID&gt

     

  • January 16, 2007 at 2:36 pm

    #683620

    well not really a spid associated with this i don't think. i'm seeing the value

    from this:

    select * from sys.dm_os_wait_stats order by [waiting_tasks_count] desc

    wait: OLEDB

    waiting_tasks_count: 601073801

    wait_time_ms: 55886480

    max_wait_time_ms: 443610

    signal_wait_time_ms: 0

    _________________________

  • January 17, 2007 at 8:55 am

    #683765

    This waitstate can be caused by things such as functions and linked servers. You may not have a problem here... These numbers do appear very high at first, but they are cumulative (since server boot). Divide the task count by the wait time and you'll see the average wait time is under 11MS which probably is not a big deal.

  • January 17, 2007 at 9:10 am

    #683771

    cool. thanks for the calculation.

    thats interesting.

    appreciate it.

    _________________________

  • December 9, 2008 at 9:12 am

    #909732

    But it is precisely these Waits that you should address. i.e. where there are many requests each experiencing (on avg) a 11ms wait. Thus the cumulative figure is significant. I read somewhere that this Wait is not a user wait & that it is a measure of how long SQL has been waiting for client app to send data. In which case it would be a User wait and you need to address issues in the app.

    Will update when I have more info.

Viewing 9 posts - 1 through 8 (of 8 total)

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