Home Dashboard Directory Help
Search

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


Status: 

Active


2
0
Sign in
to vote
Type: Bug
ID: 777221
Opened: 1/23/2013 12:01:15 AM
Access Restriction: Public
1
Workaround(s)
view
0
User(s) can reproduce this bug

Description

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
Sign in to post a comment.
Sign in to post a workaround.
Posted by Koen Verbeeck on 1/23/2013 at 12:02 AM
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.