February 4, 2015 at 11:38 pm
is it possible that this error during backup caused Sort Warning???
I sent to support of our Storage and he make result that this caused jobs which have Sort Warning....
if I checked this error on internet, i found problem with Storage or it can be also lot of fullscan and etc.
So it can be also that Order By caused some reading directly from disk and not from memory ? maybe if there is using tempdb right ?
thanks a lot
February 5, 2015 at 12:36 am
hi tony,
As best of my knowledge, this 833 error is fired in the event log generally when your server I/O response take more than 15 sec. Sometimes error in system events, issues with storage devices in OS and large wait time for PAGEIOLATCH also leads to the occurrence of this error.
Basically updating all your device drivers and performing disk system diagnose can be helpful to you.Monitor the performance of below mentioned can be helpful..
Sec/Transfer of Average Disk
Queue Length of Average Disk
Queue Length of Current Disk
Hope so this will be helpful for you and for more details can ask if possible will surely acknowledge your query.
Thanks & Regards
February 5, 2015 at 4:51 am
Yeah, it's really an issue with the servers and their configuration.
But, that's not to say that tuning won't help. Reduce the amount and number of reads you need and then latency problems, while they won't go away, their impact will be reduced.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
February 5, 2015 at 4:57 am
this support of storage is supplier so i am not sure that i can trust him....
I found few sites, i will try set counters for these and i will see,
http://www.sqlserver-dba.com/2010/11/io-requests-taking-longer-than-15-seconds-to-complete.html
http://blogs.msdn.com/b/karthick_pk/archive/2012/06/26/io_2d00_bottlenecks.aspx
https://technet.microsoft.com/en-us/magazine/jj643251.aspx
if you will have any next topic how can i find that is really problem with storage or it can be inside SQL for example lot of full scan or something else i will very appreciate
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply