Proc_getObject with nolock causes "read operation on a large object failed while sending data to the client"

Question

SharePoint 2013 code for the SharePoint Config database stored procedure dbo.proc_getObject has been changed from SharePoint 2010 with the difference of select with nolock.
I am seeing numerous Error 7886, Severity-20 errors nightly:
"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."
Here I have commented out "with (nolock)" to 'fix' the error and to align the store proc with SharePoint 2010 code : 
ALTER PROCEDURE [dbo].[proc_getObject]
@Id uniqueidentifier,
@RequestGuid uniqueidentifier = NULL OUTPUT
AS
SET NOCOUNT ON
SELECT
Id,
ParentId,
ClassId,
Name,
Status,
Version,
Properties
FROM
Objects --with (nolock)
WHERE
Id = @Id
RETURN 0
How is this stored procedure called and for what use?
Why did Microsoft make this change to SharePoint 2013 - some performance gain through dirty reads at the cost of stability? Or what could be a reason for this to happen that can be fixed?

Answer 1

GetObject retrieves any farm object that is selected (by ID). Changing this is obviously not supported, and NoLock was used to (help) prevent locks when performing a select query.
I've never seen this issue, and would guess it is unique to your environment given this is such a core piece of the SharePoint infrastructure.
Trevor Seward
Follow or contact me at...
&nbsp&nbsp
This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.