FIX: You may receive an error message when you run a CLR stored procedure or CLR function that uses a context connection in SQL Server 2005
Bug #: 50000483 (SQL Hotfix) NoticeMicrosoft distributes Microsoft SQL Server 2005 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 2005 fix release.SUMMARYThis article describes the following about this hotfix release:
SYMPTOMSYou execute a common language runtime (CLR) stored procedure or a CLR function in the SQL Server process. In the CLR stored procedure or the CLR function, you use a context connection to open a loop-back connection and execute many Transact-SQL statements. For example, you execute 1 billion Transact-SQL statements. Additionally, these Transact-SQL statements do not return result sets. For example, these Transact-SQL statements are SET statements or cursor operations. When you run the CLR stored procedure or the CLR function in SQL Server 2005, you may receive one of the following error messages: Error Message 1 Server: Msg 6535, Level 16, State 49 Note AppDomain represents the name of the application domain in which the code runs..NET Framework execution was aborted. Another query caused the AppDomain AppDomain.1 to be unloaded or an unhandled .NET exception happened. Error Message 2 Server: Msg 6532, Level 16, State 70 When this problem occurs, messages that resemble the following are logged in the SQL Server Errorlog:.NET Framework execution was aborted by escalation policy because of out of memory. 2007-01-15 14:47:46.76 spid51 AppDomain 3 (CLR_DB.dbo[runtime].2) created. 2007-01-15 14:49:48.06 spid1s AppDomain 3 (CLR_DB.dbo[runtime].2) is marked for unload due to memory pressure. 2007-01-15 14:51:23.47 spid51 Error: 6532, Severity: 16, State: 70. 2007-01-15 14:51:23.47 spid51 .NET Framework execution was aborted by escalation policy because of out of memory. 2007-01-15 14:51:53.31 spid51 AppDomain 3 (CLR_DB.dbo[runtime].2) unloaded. RESOLUTIONA supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix. If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Online Customer Services to obtain the hotfix. To submit an online request to obtain the hotfix, visit the following Microsoft Web site: http://go.microsoft.com/?linkid=6294451 (http://go.microsoft.com/?linkid=6294451) Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. To create a separate service request, visit the following Microsoft Web site: http://support.microsoft.com/contactus/?ws=support (http://support.microsoft.com/contactus/?ws=support) Note The "Hotfix download available" section and the online request forms display the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.PrerequisitesYou must have SQL Server 2005 Service Pack 1 (SP1) installed to apply this hotfix.For more information about how to obtain SQL Server 2005 Service Pack 1, click the following article number to view the article in the Microsoft Knowledge Base: 913089 (http://support.microsoft.com/kb/913089/)
How to obtain the latest service pack for SQL Server 2005
Restart informationYou do not have to restart the computer after you apply this hotfix.Registry informationYou do not have to change the registry.Hotfix file informationThis hotfix contains only those files that are required to correct the issues that this article lists. This hotfix may not contain of all the files that you must have to fully update a product to the latest build.The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel. SQL Server 2005 32-bit version
SQL Server 2005 x64-based version
SQL Server 2005 Itanium architecture version
WORKAROUNDTo work around this problem, do not use the context connection in your CLR stored procedure or CLR function. Instead, use a regular connection. STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. REFERENCESFor more information about the context connection, visit the following Microsoft Developer Network (MSDN) Web site: http://msdn2.microsoft.com/en-us/library/ms131053.aspx (http://msdn2.microsoft.com/en-us/library/ms131053.aspx) For more information about restrictions on regular connections and on context connections, visit the following MSDN Web site: http://msdn2.microsoft.com/en-us/library/ms131101.aspx (http://msdn2.microsoft.com/en-us/library/ms131101.aspx)
For more information about the naming schema for Microsoft 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
APPLIES TO
| Article Translations
|
| United States | Change | | | All Microsoft Sites |
Help and Support
Back to the top
|
