Custom ADONETDestination component.
Hi All, I am trying to create a cutom Microsoft.SqlServer.Dts.Pipeline.ADONETDestination component which will act as normal ADONETDestination + My Custom Logic. What I want is I need to process the input rows and and only add the selected rows to the database. I am not sure can I achieve this or not? Please let me know -Kannan
November 9th, 2010 6:14pm

Hi Kannan, For your request, we can use Data Flow Transformations tasks to process the data, then use the Script Component as a destination to process the input rows. Script Component is similar to ADONETDestination, please use it directly instead of custom ADONETDestination. For more informaiton about Script Component, please see: http://msdn.microsoft.com/en-us/library/ms137640.aspx If you have any more questions, please feel free to ask. Thanks, Jin ChenJin Chen - MSFT
Free Windows Admin Tool Kit Click here and download it now
November 11th, 2010 6:34am

Thanks Jin! But my requirement is something ifferent. We have many ETL package asscoiated with different different application. What we want to use before it puts the data into the final destination, we need to process the rows and apply some rules ( by calling a rule engine) on it. Once the rule engine return true ( meaning validation on the row was succeeded.), we need to add that row into a separate buffer ( this process continues for all the rows) and puts into the database. I posted one in the forum, Please look at the following link for the reference. http://social.msdn.microsoft.com/Forums/en-US/sqlintegrationservices/thread/6452c3d7-8257-4769-8346-4427fef9cf6f Where I am stuck is how can I build my own pipeline buffer and put the processed rows. Thanks -Kannan
November 11th, 2010 9:54am

You should look at using the Script component first to work out your logic. You can then take that code and paste it - with a lot more modifications - into a custom component. There are tons of examples here that should give you something fairly close to start from. Look for a synchronous component that has one input, but several outputs to start with. That will be the simplest model to work from. Talk to me now on
Free Windows Admin Tool Kit Click here and download it now
November 18th, 2010 10:59am

I think you should consider using standard components and data flow using the script component to instantiate your rule engine and create multiple outputs. The effort in developing a target component may be excessive for the purpose, existing alternatives. I'm with Jin in his tip.Vctor M. Snchez Garca (ES) (BI) Hope this help. Please vote if you find this posting was helpful. if this is an answer to your question, please mark it.
November 18th, 2010 11:11am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics