Select the product you need help with

FIX: "Non-yielding Scheduler" error message when you insert a record that contains large object (LOB) data into a snapshot database in SQL Server 2008 or in SQL Server 2008 R2

Article ID: 2770891 - View products that this article applies to.

Symptoms

Consider the following scenario:

You run an INSERT statement to insert a record that contains large object (LOB) data into a snapshot database in Microsoft SQL Server 2008 or in Microsoft SQL Server 2008 R2.
You receive the following error message:
Failed to update database "<DatabaseName>" because the database is read-only.
You restart SQL Server, and then you try to insert the record again.

In this scenario, the INSERT statement runs in an infinite loop and returns no result. Additionally, a "Non-yielding Scheduler" error message is logged in the SQL Server error log, and a dump file is generated.

Back to the top | Give Feedback

Resolution

Cumulative update information

Cumulative Update 4 for SQL Server 2008 R2 SP2

The fix for this issue was first released in Cumulative Update 4. For more information about how to obtain this cumulative update package for SQL Server 2008 R2 SP 2, click the following article number to view the article in the Microsoft Knowledge Base:

2777358

(http://support.microsoft.com/kb/2777358/ )

Cumulative update package 4 for SQL Server 2008 R2 Service Pack 2

Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 R2 SP 2 fix release. We recommend that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

2730301

(http://support.microsoft.com/kb/2730301/ )

The SQL Server 2008 R2 builds that were released after SQL Server 2008 R2 Service Pack 2 was released

Cumulative update package 10 for SQL Server 2008 R2 Service Pack 1

The fix for this issue was first released in Cumulative Update 10. For more information about how to obtain this cumulative update package for SQL Server 2008 R2 SP1, click the following article number to view the article in the Microsoft Knowledge Base:

2783135

(http://support.microsoft.com/kb/2783135/ )

Cumulative update package 10 for SQL Server 2008 R2 SP1

Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 R2 SP1 fix release. We recommend that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

2567616

(http://support.microsoft.com/kb/2567616/ )

The SQL Server 2008 R2 builds that were released after SQL Server 2008 R2 Service Pack 1 was released

Cumulative update 8 for SQL Server 2008 Service Pack 3 (SP3)

The fix for this issue was first released in Cumulative Update 8. For more information about how to obtain this cumulative update package for SQL Server 2008 Service Pack 3, click the following article number to view the article in the Microsoft Knowledge Base:

2771833

(http://support.microsoft.com/kb/2771833/ )

Cumulative update package 8 for SQL Server 2008 Service Pack 3

Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 Service Pack 3 fix release. We recommend that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

2629969

(http://support.microsoft.com/kb/2629969/ )

The SQL Server 2008 builds that were released after SQL Server 2008 Service Pack 3 was released

Back to the top | Give Feedback