FIX: CLR stored procedure returns NULL after it is recompiled in SQL Server 2008 R2 or in SQL Server 2008

Article ID: 2536225 - View products that this article applies to.
Microsoft distributes Microsoft SQL Server 2008 R2 or Microsoft SQL Server 2008 fixes as one downloadable file. Because the fixes are cumulative, each new release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 R2 or SQL Server 2008 fix release.
Expand all | Collapse all

On This Page

SYMPTOMS

Consider the following scenario:
  • You create a common language runtime (CLR) stored procedure for a Microsoft SQL Server 2008 R2 or a Microsoft SQL Server 2008 database.
  • The CLR stored procedure is implemented as a public static method that returns an integer value in the Microsoft .NET Framework.
  • You run an application that calls the CLR stored procedure. The CLR stored procedure returns a correct value.
  • You perform some operations that recompile the execution plan for the CLR stored procedure.

    Note For more information about how to recompile the execution plan for the stored procedure, see the "More information" section.
  • You run the application again.
In this scenario, the CLR stored procedure incorrectly returns a NULL value. Additionally, you have to restart the SQL Server service to recover from this issue.
Back to the top | Give Feedback

RESOLUTION

Cumulative update information

SQL Server 2008 Service Pack 3

The fix for this issue was first released in Cumulative Update 2 for SQL Server 2008 Service Pack 3. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
2633143
(http://support.microsoft.com/kb/2633143/LN/ )
Cumulative update package 2 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 fix release. Microsoft recommends 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/LN/ )
The SQL Server 2008 builds that were released after SQL Server 2008 Service Pack 3 was released
Microsoft SQL Server 2008 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2008 Service Pack 3 hotfix to an installation of SQL Server 2008 Service Pack 3. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack.

SQL Server 2008 R2 Service Pack 1

The fix for this issue was first released in Cumulative Update 2 for SQL Server 2008 R2 Service Pack 1. For more information about how to obtain this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
2567714
(http://support.microsoft.com/kb/2567714/ )
Cumulative Update package 2 for SQL Server 2008 R2 Service Pack 1
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 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

SQL Server 2008 R2

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 R2, click the following article number to view the article in the Microsoft Knowledge Base:
2534352
(http://support.microsoft.com/kb/2534352/ )
Cumulative Update package 8 for SQL Server 2008 R2
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 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:
981356
(http://support.microsoft.com/kb/981356/ )
The SQL Server 2008 R2 builds that were released after SQL Server 2008 R2 was released
Back to the top | Give Feedback

MORE INFORMATION

To recompile the execution plan for the stored procedure, perform any of the following operations:
  • Run the DBCCFREEPROCCACHE statement.
  • Run one of the following statements against a table or view:
    • ALTER TABLE
    • ALTER VIEW
  • Run an execution plan that changes or deletes indexes.
  • Perform an Update operation on the statistics that are used by the execution plan.

    Note You can run a statement to perform the Update operation, or the Update operation can be performed automatically.
  • Run the sp_recompile statement.
  • Make many changes to keys.

    For example, use a user account that updates a table that is referenced by a statement to run the INSERT or DELETE statement.
  • Insert or delete many rows from a table that contains triggers.
  • Use the WITH RECOMPILE option to run a stored procedure.
Back to the top | Give Feedback

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Back to the top | Give Feedback

REFERENCES

For more information about CLR stored procedures, visit the following MSDN website:
General information about CLR stored procedures
(http://msdn.microsoft.com/en-us/library/ms131094.aspx)


For more information about the Incremental Servicing Model for SQL Server, click the following article number to view the article in the Microsoft Knowledge Base:
935897
(http://support.microsoft.com/kb/935897/ )
An Incremental Servicing Model is available from the SQL Server team to deliver hotfixes for reported problems
For more information about the naming schema for SQL Server updates, click the following article number to view the article in the Microsoft Knowledge Base:
822499
(http://support.microsoft.com/kb/822499/ )
New naming schema for Microsoft SQL Server software update packages
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684
(http://support.microsoft.com/kb/824684/ )
Description of the standard terminology that is used to describe Microsoft software updates
Back to the top | Give Feedback

Properties

Article ID: 2536225 - Last Review: November 22, 2011 - Revision: 4.0
APPLIES TO
  • Microsoft SQL Server 2008 R2 Developer
  • Microsoft SQL Server 2008 R2 Enterprise
  • Microsoft SQL Server 2008 R2 Standard
  • Microsoft SQL Server 2008 R2 Web
  • Microsoft SQL Server 2008 R2 Workgroup
  • Microsoft SQL Server 2008 Developer
  • Microsoft SQL Server 2008 Enterprise
  • Microsoft SQL Server 2008 Standard
  • Microsoft SQL Server 2008 Web
  • Microsoft SQL Server 2008 Workgroup
Keywords: 
kbqfe kbfix kbexpertiseadvanced kbsurveynew KB2536225
Back to the top | Give Feedback

Give Feedback

 
Back to the topBack to the top