Select the product you need help with
"Bulk Insert with another outstanding result set should be run with XACT_ABORT on" error message may occur when you run a DTC or MARS transaction in SQL Server 2008 or SQL Server 2008 R2Article ID: 2412203 - View products that this article applies to. Microsoft distributes Microsoft SQL Server 2008 and Microsoft SQL Server 2008 R2 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 or SQL Server 2008 R2 fix release. On This PageSYMPTOMSConsider the following scenario:
Error: 595, Severity: 16, State: 1 Bulk Insert with another outstanding result set should be run with XACT_ABORT on. CAUSEThis issue occurs because SQL Server incorrectly detects a MARS deadlock. SQL Server avoids deadlocks that may occur when you start a MARS or DTC transaction. However, SQL Server does not check whether the FIRE_TRIGGERS option is specified in the BULK INSERT statement. Note
RESOLUTIONCumulative update informationSQL Server 2008The fix for this issue was first released in Cumulative Update 11 for SQL Server 2008 Service Pack 1. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:2413738 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:
(http://support.microsoft.com/kb/2413738/LN/
)
Cumulative update package 11 for SQL Server 2008 Service Pack 1970365 Microsoft SQL Server 2008 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2008 Service Pack 1 hotfix to an installation of SQL Server 2008 Service Pack 1. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack.
(http://support.microsoft.com/kb/970365/LN/
)
The SQL Server 2008 builds that were released after SQL Server 2008 Service Pack 1 was released SQL Server 2008 R2The fix for this issue was first released in Cumulative Update 5. 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: 2438347 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:
(http://support.microsoft.com/kb/2438347/
)
Cumulative Update package 5 for SQL Server 2008 R2 981356
(http://support.microsoft.com/kb/981356/
)
The SQL Server 2008 R2 builds that were released after SQL Server 2008 R2 was releasedSQL Server 2008 Service Pack 2The fix for this issue was first released in Cumulative Update 2 for SQL Server 2008 Service Pack 2. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:2467239 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:
(http://support.microsoft.com/kb/2467239/LN/
)
Cumulative update package 2 for SQL Server 2008 Service Pack 22402659 Microsoft SQL Server 2008 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2008 Service Pack 2 hotfix to an installation of SQL Server 2008 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.
(http://support.microsoft.com/kb/2402659/LN/
)
The SQL Server 2008 builds that were released after SQL Server 2008 Service Pack 2 was released 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 BULK INSERT statement, visit the following MSDN website: General information about the BULK INSERT statement For more information about the OLE DB destination, visit the following MSDN website:
(http://msdn.microsoft.com/en-us/library/ms188365(v=SQL.100).aspx)
General information about the OLE DB destination 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:
(http://msdn.microsoft.com/en-us/library/ms141237(v=SQL.100).aspx)
935897 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:
(http://support.microsoft.com/kb/935897/
)
An Incremental Servicing Model is available from the SQL Server team to deliver hotfixes for reported problems
822499 For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/822499/
)
New naming schema for Microsoft SQL Server software update packages824684
(http://support.microsoft.com/kb/824684/
)
Description of the standard terminology that is used to describe Microsoft software updatesPropertiesArticle ID: 2412203 - Last Review: January 17, 2011 - Revision: 3.0 APPLIES TO
|
Back to the top
