Article ID: 2508239 - View products that this article applies to.
Consider the following scenario:
This occurs because SSIS incorrectly calls “SET ROWCOUNT 1” on the session that is executing the INSERT AFTER trigger. This causes the trigger to prematurely stop execution after it inserts the first row.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section of this article when you apply the fix documented in 975950. This hotfix is also included in the following updates:
(http://support.microsoft.com/default.aspx?scid=kb;EN-US;976951)So, the issue affects any builds of the respective product that contain this fix. You can use the following table as quick reference:
Collapse this tableExpand this table
To workaround the problem do the following in the OLE DB Destination editor:
For additional information refer to the following topic in SQL Server Books Online:
Example: The following trigger uses UNION clause to inserts multiple rows in the destination table (MyTable)
Because of the problem discussed in this article, when an SSIS package inserts any row into the table, the trigger only inserts the first row (7,7) and stops execution instead of inserting 3 rows.
(http://go.microsoft.com/fwlink/?LinkId=151500)for other considerations.
Article ID: 2508239 - Last Review: March 19, 2011 - Revision: 1.0
Contact us for more help
Connect with Answer Desk for expert help.