Occurs when SQL Server calls the SQL Server Native Client OLE DB Provider. This wait type is not used for synchronization. Instead, it indicates the duration of calls to the OLE DB provider. Information from Microsoft®
Waitopedia is a comprehensive resource of information about SQL Server waits.
The description shown below is the top answer as voted by the Spotlight community.
The charts are based on 2.1 TB of data collected from 4207 instances uploaded by 323 Spotlight users over an 8 week period.
|
Occurs when SQL Server calls the SQL Server Native Client OLE DB Provider. This wait type is not used for synchronization. Instead, it indicates the duration of calls to the OLE DB provider. Information from Microsoft® |
|
|
OLEDB waits occur when the network cannot accept the output SQL Server is sending to a client as fast as SQL Server is able to send it. This occurs either because the network is slow, or because the client machine is slow and can't accept data from the network as fast as SQL Server is trying to send it. In any event, the time spent waiting is included in the duration that SQL Server records for execution of the query, and if this wait stat is occurring, SQL Server will appear to be at fault because of slow execution times, when in fact the execution time is including time that SQL Server can do nothing about. |
Actually, what I described above is ASYNC_NETWORK_IO, which is similar. OLEDB occurs when the client cannot SEND data as fast as SQL Server is able to receive it, either because of network speed, or because of apparent network speed actually due to a slow client. This can occur when uploading or inserting many records in a single batch.
–
2837 days ago
|
This wait is very common for most instances
For each of 4207 instances, we ranked OLEDB on how frequent it is compared to all other recent waits. The chart shows the total of all rankings.
For 86 % of hours with this wait, average wait time is less than 0.15 ms
For each instance, we found all the recent hours when it had a OLEDB wait. We found the average latency for each of those hours.
2554 instances contributed data to this chart