December 16, 2009 at 7:26 am
Hi All
I am seeing this error being logged in my SQL 2005
A read operation on a large object failed while sending data to the client. A common cause for this is if the application is running in READ UNCOMMITTED isolation level. This connection will be terminated.
PLEASE GIVE ME ANY SOLUTIONS
Regards,
Jayesh
December 16, 2009 at 8:33 am
First question is, are you running read_uncommitted? If so, you might need to reconsider that choice. I don't recommend using that connection setting for most systems anyway.
If the read is taking so long that other processes are deleting the objects before you can finish, you might need to tune the query. Again, avoiding read_uncommitted is still the better option.
"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
December 16, 2009 at 9:11 am
above error occur on production server and this error occur on 11/12/2009 and then continue but before 11/12/09 this error not occured . so what the exact problem and better solutions.
December 16, 2009 at 9:13 am
Hi
above error occur on production server and this error occur on 11/12/2009 and then continue but before 11/12/09 this error not occured . so what the exact problem and better solutions.
Jayesh
December 16, 2009 at 9:24 am
I'm sorry, I'm not there, so I can only answer based on the information you've provided.
From what you've said, a long running process was reading some large piece of data. Because you're running read_uncommitted, you're not even putting shared locks on the data, so another process came long and deleted the data before the first process could finish reading it. That gave you the error.
Based on what you've said, again, it's not enough information, I'd suggest removing read_uncommitted and going with read_committed (or if you were on 2008, I'd suggest read_committed_snapshot).
"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
December 16, 2009 at 12:01 pm
Also do a consistency check, make sure there are no errors.
DBCC CHECKDB (<Database Name>) WITH NO_INFOMSGS, ALL_ERRORMSGS
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply