Bug #: 50000483 (SQL Hotfix)
Microsoft 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.
Summary
This article describes the following about this hotfix release:
- The issues that are fixed by this hotfix package
- The prerequisites for installing the hotfix package
- Information about whether you must restart the computer after you install the hotfix package
- Information about whether the hotfix package is replaced by any other hotfix package
- Information about whether you must make any registry changes
- The files that are contained in the hotfix package
Symptoms
You 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:
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
.NET Framework execution was aborted. Another query caused the AppDomain AppDomain.1 to be unloaded or an unhandled .NET exception happened.
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
.NET Framework execution was aborted by escalation policy because of out of memory.
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.
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.
Resolution
A 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, contact Microsoft Customer Service and Support to obtain the hotfix.
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. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays 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.
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:
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.
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, contact Microsoft Customer Service and Support to obtain the hotfix.
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. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays 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.
Prerequisites
You 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:
Restart information
You do not have to restart the computer after you apply this hotfix.Registry information
You do not have to change the registry.Hotfix file information
This 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
| File name | File version | File size | Date | Time | Platform |
|---|---|---|---|---|---|
| Logread.exe | 2005.90.2206.0 | 398,112 | 17-Nov-2006 | 03:16 | x86 |
| Microsoft.analysisservices.adomdclient.dll | 9.0.2206.0 | 543,520 | 17-Nov-2006 | 03:16 | x86 |
| Microsoft.analysisservices.dll | 9.0.2206.0 | 1,215,264 | 17-Nov-2006 | 03:16 | x86 |
| Microsoft.sqlserver.sqlenum.dll | 9.0.2206.0 | 908,064 | 17-Nov-2006 | 03:16 | x86 |
| Ms.as.deployengine.dll | 9.0.2206.0 | 138,016 | 17-Nov-2006 | 03:16 | x86 |
| Ms.ss.mgdsqldumper.dll | 2005.90.2206.0 | 75,552 | 17-Nov-2006 | 03:16 | x86 |
| Msasxpress.dll | 9.0.2206.0 | 22,304 | 17-Nov-2006 | 03:16 | x86 |
| Msgprox.dll | 2005.90.2206.0 | 197,920 | 17-Nov-2006 | 03:16 | x86 |
| Msmdlocal.dll | 9.0.2206.0 | 15,614,752 | 17-Nov-2006 | 03:16 | x86 |
| Msmdredir.dll | 9.0.2206.0 | 3,990,304 | 17-Nov-2006 | 03:16 | x86 |
| Replprov.dll | 2005.90.2206.0 | 547,616 | 17-Nov-2006 | 03:16 | x86 |
| Replrec.dll | 2005.90.2206.0 | 782,112 | 17-Nov-2006 | 03:16 | x86 |
| Sqlaccess.dll | 2005.90.2206.0 | 347,936 | 17-Nov-2006 | 03:16 | x86 |
| Sqlagent90.exe | 2005.90.2206.0 | 318,752 | 17-Nov-2006 | 03:16 | x86 |
| Sqlservr.exe | 2005.90.2206.0 | 28,964,696 | 17-Nov-2006 | 03:16 | x86 |
| Xmlsub.dll | 2005.90.2206.0 | 192,800 | 17-Nov-2006 | 03:10 | x86 |
| Xpstar90.dll | 2005.90.2206.0 | 292,640 | 17-Nov-2006 | 03:10 | x86 |
| Xpstar90.rll | 2005.90.2206.0 | 152,864 | 17-Nov-2006 | 03:16 | Not Applicable |
SQL Server 2005 x64-based version
| File name | File version | File size | Date | Time | Platform |
|---|---|---|---|---|---|
| Logread.exe | 2005.90.2206.0 | 522,528 | 16-Nov-2006 | 18:02 | x64 |
| Microsoft.analysisservices.adomdclient.dll | 9.0.2206.0 | 543,520 | 16-Nov-2006 | 18:02 | x86 |
| Microsoft.analysisservices.dll | 9.0.2206.0 | 1,215,264 | 17-Nov-2006 | 03:16 | x86 |
| Microsoft.sqlserver.mgdsqldumper.dll | 2005.90.2206.0 | 91,424 | 16-Nov-2006 | 18:02 | x64 |
| Microsoft.sqlserver.sqlenum.dll | 9.0.2206.0 | 875,296 | 16-Nov-2006 | 18:02 | x86 |
| Microsoft.analysisservices.deploymentengine.dll | 9.0.2206.0 | 138,016 | 17-Nov-2006 | 03:16 | x86 |
| Msasxpress.dll | 9.0.2206.0 | 27,424 | 16-Nov-2006 | 18:02 | x64 |
| Msgprox.dll | 2005.90.2206.0 | 259,360 | 16-Nov-2006 | 18:02 | x64 |
| Msmdlocal.dll | 9.0.2206.0 | 15,614,752 | 17-Nov-2006 | 03:16 | x86 |
| Msmdredir.dll | 9.0.2206.0 | 3,990,304 | 17-Nov-2006 | 03:16 | x86 |
| Replprov.dll | 2005.90.2206.0 | 745,248 | 16-Nov-2006 | 18:02 | x64 |
| Replrec.dll | 2005.90.2206.0 | 1,008,416 | 16-Nov-2006 | 18:02 | x64 |
| Sqlaccess.dll | 2005.90.2206.0 | 355,104 | 16-Nov-2006 | 18:02 | x86 |
| Sqlagent90.exe | 2005.90.2206.0 | 389,920 | 16-Nov-2006 | 18:02 | x64 |
| Sqlservr.exe | 2005.90.2206.0 | 39,371,040 | 16-Nov-2006 | 18:02 | x64 |
| Xmlsub.dll | 2005.90.2206.0 | 317,216 | 16-Nov-2006 | 18:02 | x64 |
| Xpstar90.dll | 2005.90.2206.0 | 540,960 | 16-Nov-2006 | 18:02 | x64 |
| Xpstar90.rll | 2005.90.2206.0 | 153,376 | 16-Nov-2006 | 18:02 | Not Applicable |
SQL Server 2005 Itanium architecture version
| File name | File version | File size | Date | Time | Platform |
|---|---|---|---|---|---|
| Logread.exe | 2005.90.2206.0 | 1,095,456 | 16-Nov-2006 | 12:14 | IA-64 |
| Microsoft.analysisservices.adomdclient.dll | 9.0.2206.0 | 543,520 | 16-Nov-2006 | 12:14 | x86 |
| Microsoft.analysisservices.deploymentengine.dll | 9.0.2206.0 | 138,016 | 17-Nov-2006 | 03:16 | x86 |
| Microsoft.analysisservices.dll | 9.0.2206.0 | 1,215,264 | 17-Nov-2006 | 03:16 | x86 |
| Microsoft.sqlserver.mgdsqldumper.dll | 2005.90.2206.0 | 163,104 | 16-Nov-2006 | 12:14 | IA-64 |
| Microsoft.sqlserver.sqlenum.dll | 9.0.2206.0 | 875,296 | 16-Nov-2006 | 12:14 | x86 |
| Msasxpress.dll | 9.0.2206.0 | 55,072 | 16-Nov-2006 | 12:14 | IA-64 |
| Msgprox.dll | 2005.90.2206.0 | 542,496 | 16-Nov-2006 | 12:14 | IA-64 |
| Msmdlocal.dll | 9.0.2206.0 | 48,610,080 | 16-Nov-2006 | 12:14 | IA-64 |
| Msmdredir.dll | 9.0.2206.0 | 6,244,128 | 16-Nov-2006 | 12:14 | Not Applicable |
| Replprov.dll | 2005.90.2206.0 | 1,617,184 | 16-Nov-2006 | 12:14 | IA-64 |
| Replrec.dll | 2005.90.2206.0 | 2,141,472 | 16-Nov-2006 | 12:14 | IA-64 |
| Sqlaccess.dll | 2005.90.2206.0 | 349,472 | 16-Nov-2006 | 12:14 | x86 |
| Sqlagent90.exe | 2005.90.2206.0 | 1,141,024 | 16-Nov-2006 | 12:14 | IA-64 |
| Sqlservr.exe | 2005.90.2206.0 | 72,259,872 | 16-Nov-2006 | 12:14 | IA-64 |
| Xmlsub.dll | 2005.90.2206.0 | 590,624 | 16-Nov-2006 | 12:14 | IA-64 |
| Xpstar90.dll | 2005.90.2206.0 | 951,072 | 16-Nov-2006 | 12:14 | IA-64 |
| Xpstar90.rll | 2005.90.2206.0 | 152,352 | 16-Nov-2006 | 12:14 | Not Applicable |
Workaround
To work around this problem, do not use the context connection in your CLR stored procedure or CLR function. Instead, use a regular connection.
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
References
For more information about the context connection, visit the following Microsoft Developer Network (MSDN) Web site: For more information about restrictions on regular connections and on context connections, visit the following MSDN Web site: 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:
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base: