Microsoft KB Archive/940210

= FIX: Error message when you try to insert more than 3 megabytes of data into a distributed partitioned view in SQL Server 2005: &quot;A system assertion check has failed&quot; =

Article ID: 940210

Article Last Modified on 8/8/2007

-

APPLIES TO


 * Microsoft SQL Server 2005 Developer Edition
 * Microsoft SQL Server 2005 Enterprise Edition
 * Microsoft SQL Server 2005 Standard Edition
 * Microsoft SQL Server 2005 Standard X64 Edition
 * Microsoft SQL Server 2005 Standard Edition for Itanium-based Systems
 * Microsoft SQL Server 2005 Enterprise X64 Edition
 * Microsoft SQL Server 2005 Enterprise Edition for Itanium-based Systems
 * Microsoft SQL Server 2005 Workgroup Edition

-



Bug #: 50001449 (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.



SYMPTOMS
Consider the following scenario. You have more than one instance of Microsoft SQL Server 2005. In each instance, a table contains an image column. You create a distributed partitioned view on one of the instances. The distributed partitioned view references more than one table in the instances. Then, you try to insert more than 3 megabytes (MB) of data into the distributed partitioned view. In this scenario, you receive the following error message:

Location: wrkspace.cpp:440

Expression: !PSess ->FHasWorkspaceRef

SPID:

Process ID:

Msg 3624, Level 20, State 1, Server, Line 3

A system assertion check has failed. Check the SQL Server error log for details

Msg 3985, Level 16, State 2, Server, Line 3

An error occurred during the changing of transaction context. This is usually caused by low memory in the system. Try to free up more memory.



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

939537 Cumulative update package 3 for SQL Server 2005 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 2005 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:

937137 The SQL Server 2005 builds that were released after SQL Server 2005 Service Pack 2 was released

Microsoft SQL Server 2005 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2005 Service Pack 2 hotfix to an installation of SQL Server 2005 Service Pack 2. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack.



STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the &quot;Applies to&quot; section.



MORE INFORMATION
For more information about what files are changed, and for information about any prerequisites to apply the cumulative update package that contains the hotfix that is described in this Microsoft Knowledge Base article, click the following article number to view the article in the Microsoft Knowledge Base:

939537 Cumulative update package 3 for SQL Server 2005 Service Pack 2

