SSIS package with Term Extraction only works with RunInOptimizedMode set to False

SSIS package with Term Extraction only works with RunInOptimizedMode set to False by Koen Verbeeck

Active

Type:	Bug
ID:	777221
Opened:	1/23/2013 12:01:15 AM
Access Restriction:	Public

Workaround(s)

view

User(s) can reproduce this bug

I designed a test package with a simple source, a destination and a term extraction component. Since the error handling of the term extraction component is by default set to "Redirect rows to error output", I added a multicast to the error output to serve as a sort of trash destination, since I'm not interested in possible error rows. The package runs succesfully in BIDS, but crashes when run with DTEXEC. When the property RunInOptimized mode is set to False, the package runs succesfully with DTEXEC.

For more information, screenshots and error messages, see this thread on the MSDN forum:
http://social.msdn.microsoft.com/Forums/en-US/sqlintegrationservices/thread/6a63b64b-ed40-4427-9da6-87af5a3fcd92/

Details (expand)

English

SQL Server 2008 R2

Integration Services (DTS)

Windows Server 2008 R2 (all editions) (SP1)

US English

Create a simple package as described in the forum thread and make sure the error path of the term extraction component is connected to a multicast. Because a multicast doesn't do anything (no side effects), SSIS will optimize this by removing the error path, resulting in the crash.

The package crashes when run through the command line using DTEXEC.
The term extraction component doesn't produce an output.

The package should run succesfully and produce the expected results (in other words, a flat file containing the terms and their score).

0 attachments

A possible work around is to not use multicast, but a component with actual side effects, such as a rowcount or a destination component. Or you could configure the term extraction component to not redirect error rows, but ignore them or fail the component.