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.
Symptoms
Consider the following scenario:
-
You run an application of Microsoft SQL Server that has a Distributed Transaction Coordinator (DTC) or Multiple Active Result Sets (MARS) transaction configured. For example, you run Microsoft SQL Server Integration Services that starts a DTC or MARS transaction.
-
You start a BULK LOAD operation as a part of the DTC or MARS transaction to a target table. The FIRE_TRIGGERS option is not specified in a BULK INSERT statement of the BULK LOAD operation.Note A BULK LOAD operation runs a BULK INSERT statement.
-
You start another BULK LOAD operation or a standard data manipulation language (DML) operation for another target table while the first BULK LOAD operation runs. These parallel operations are in the same DTC or MARS transaction. .
In this scenario, you may receive the following error message:
Error: 595, Severity: 16, State: 1Bulk Insert with another outstanding result set should be run with XACT_ABORT on.
Cause
This 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
-
For more information about how to avoid a MARS deadlock in SQL Server, see the "Interleaved Execution" section of the "Multiple Active Result Sets (MARS) in SQL Server 2005" article on Microsoft Developer Network (MSDN) website.For more information about the "Multiple Active Result Sets (MARS) in SQL Server 2005" article, visit the following Microsoft Developer Network (MSDN) website:
The "Multiple Active Result Sets (MARS) in SQL Server 2005" article
Resolution
Cumulative update information
SQL Server 2008
The 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 Cumulative update package 11 for SQL Server 2008 Service Pack 1Note 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:
970365 The SQL Server 2008 builds that were released after SQL Server 2008 Service Pack 1 was released 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.
SQL Server 2008 R2
The 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 Cumulative Update package 5 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 The SQL Server 2008 R2 builds that were released after SQL Server 2008 R2 was released
SQL Server 2008 Service Pack 2
The 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 Cumulative update package 2 for SQL Server 2008 Service Pack 2Note 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:
2402659 The SQL Server 2008 builds that were released after SQL Server 2008 Service Pack 2 was released 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.
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 BULK INSERT statement, visit the following MSDN website:
General information about the BULK INSERT statementFor more information about the OLE DB destination, visit the following MSDN website:
General information about the OLE DB destinationFor 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 An Incremental Servicing Model is available from the SQL Server team to deliver hotfixes for reported problemsFor more information about the naming schema for SQL Server updates, click the following article number to view the article in the Microsoft Knowledge Base:
822499New naming schema for Microsoft SQL Server software update packagesFor more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates
