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

SQLServerCentral is supported by Red Gate Software Ltd.

Popular Topics

Home

Members

Calendar

Who's On

Home » SQL Server 2005 » Administering » OLEDB Wait Type.... why, and how to...

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

Rate Topic

Display Mode

Topic Options

Author

Message

neotokyo

Posted Monday, January 15, 2007 1:15 PM

Old Hand

Group: General Forum Members
Last Login: Tuesday, September 25, 2012 2:48 PM
Points: 345, Visits: 234

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

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

_________________________

Post #336973

neotokyo

Posted Tuesday, January 16, 2007 7:17 AM

Old Hand

Group: General Forum Members
Last Login: Tuesday, September 25, 2012 2:48 PM
Points: 345, Visits: 234

any ideas would be greatly appreciated.

thanks in advance.

_________________________

Post #337134

Balmukund Lakhani-269523

Posted Tuesday, January 16, 2007 1:10 PM

Old Hand

Group: General Forum Members
Last Login: Monday, April 01, 2013 3:41 AM
Points: 339, Visits: 240

any linked sevrer?

Post #337294

neotokyo

Posted Tuesday, January 16, 2007 2:11 PM

Old Hand

Group: General Forum Members
Last Login: Tuesday, September 25, 2012 2:48 PM
Points: 345, Visits: 234

thanks for the reply...

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

_________________________

Post #337313

Balmukund Lakhani-269523

Posted Tuesday, January 16, 2007 2:21 PM

Old Hand

Group: General Forum Members
Last Login: Monday, April 01, 2013 3:41 AM
Points: 339, Visits: 240

can you please check

DBCC INPUTBUFFER(<SPID>

Post #337321

neotokyo

Posted Tuesday, January 16, 2007 2:36 PM

Old Hand

Group: General Forum Members
Last Login: Tuesday, September 25, 2012 2:48 PM
Points: 345, Visits: 234

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

_________________________

Post #337325

Steve Goodwin-362749

Posted Wednesday, January 17, 2007 8:55 AM

Grasshopper

Group: General Forum Members
Last Login: Friday, March 23, 2007 7:34 AM
Points: 16, Visits: 1

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.

Post #337507

neotokyo

Posted Wednesday, January 17, 2007 9:10 AM

Old Hand

Group: General Forum Members
Last Login: Tuesday, September 25, 2012 2:48 PM
Points: 345, Visits: 234

cool. thanks for the calculation.

thats interesting.

appreciate it.

_________________________

Post #337514

Preet_S

Posted Tuesday, December 09, 2008 9:12 AM

SSC Veteran

Group: General Forum Members
Last Login: Wednesday, May 01, 2013 5:15 AM
Points: 236, Visits: 235

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.

Post #616248

« Prev Topic | Next Topic »

Permissions