September 21, 2009 at 5:17 pm
I am new to this SQL Server stuff. I am seeing the error below in our Project Server
running on SQL Server 2005.
Message
Sourcespid77
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.
Message
Error: 7886, Severity: 20, State: 1.
Being new to SQL Server, how do i find out which session/user caused it. sp_who did not bring up spid77;
It showed 76 , 78 etc but not 77 (I verified it). Possibly it got disconnected by the time i connected.
I am not seeing anything other than the above messages in the SQL Server error logs.
1. How do i see who/what query caused it? Which database it was run on?
2. Going forward what i need to do (Set up Profiler?) to troubleshoot such issues?
3. How do i see the session history? Where does SQL Server keep it?
4. If it occurs repeatedly, would enabling AWE help?
Currently AWE is not enabled but for the SQL Server Properties, the minumum is defined as 128MB
and the maximum is defined as 2147483647Mb.
September 22, 2009 at 12:20 am
gk-411903 (9/21/2009)
I am new to this SQL Server stuff. I am seeing the error below in our Project Serverrunning on SQL Server 2005.
Message
Sourcespid77
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.
Message
Error: 7886, Severity: 20, State: 1.
Being new to SQL Server, how do i find out which session/user caused it. sp_who did not bring up spid77;
It showed 76 , 78 etc but not 77 (I verified it). Possibly it got disconnected by the time i connected.
I am not seeing anything other than the above massages in the SQL Server error logs.
1. How do i see who/what query caused it? Which database it was run on?
2. Going forward what i need to do (Set up Profiler?) to troubleshoot such issues?
3. How do i see the session history? Where does SQL Server keep it?
4. If it occurs repeatedly, would enabling AWE help?
Currently AWE is not enabled but for the SQL Server Properties, the minumum is defined as 128MB
and the maximum is defined as 2147483647Mb.
Hi GK
firstly SP_WHO2 only shows current processes and not the past processes.
in your case the process id is already mentioned in the error message "SPID22". It means that the "Server Process ID 22".
For the name of database refer to some additional error massages in SQL Server Error logs And/or Windows events logs (you can filter windows for event only from MSSQL).
you can setup profiler trace but make sure its not hampering your performance.
Since, SQL Server 2005 has a built in default trace, I suggest you explore this from SQL Server Books On Line and ask incase you have any doubt in it. you may not need to run a profiler trace if you go through Default Trace and its benefits in BOL.
HTH.
September 22, 2009 at 12:46 am
gk-411903 (9/21/2009)
I am new to this SQL Server stuff. I am seeing the error below in our Project Serverrunning on SQL Server 2005.
Message
Sourcespid77
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.
Message
Error: 7886, Severity: 20, State: 1.
Being new to SQL Server, how do i find out which session/user caused it. sp_who did not bring up spid77;
It showed 76 , 78 etc but not 77 (I verified it). Possibly it got disconnected by the time i connected.
I am not seeing anything other than the above messages in the SQL Server error logs.
1. How do i see who/what query caused it? Which database it was run on?
2. Going forward what i need to do (Set up Profiler?) to troubleshoot such issues?
3. How do i see the session history? Where does SQL Server keep it?
4. If it occurs repeatedly, would enabling AWE help?
Currently AWE is not enabled but for the SQL Server Properties, the minumum is defined as 128MB
and the maximum is defined as 2147483647Mb.
As mentioned in previous post, you can check the default trace. profiler can be used but it is of more use for repeatable error finding, when you can re-run tasks and see what is failing. session information is isolated, depends on what sort of information you are after. and no AWE wouldnt have no effect on this. AWE is used to allow sql server to access memory over 4 gb.
Just to add to this post, sometimes you can get this error, if the statement that ran is using a nolock hint or the operation is being blocked by another process.
--------------------------------------------------------------------------------------
[highlight]Recommended Articles on How to help us help you and[/highlight]
[highlight]solve commonly asked questions[/highlight]
Forum Etiquette: How to post data/code on a forum to get the best help by Jeff Moden[/url]
Managing Transaction Logs by Gail Shaw[/url]
How to post Performance problems by Gail Shaw[/url]
Help, my database is corrupt. Now what? by Gail Shaw[/url]
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply