|
Home > Archive > MS SQL Server DTS > March 2006 > Script component in ssis with multiple inputs
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Script component in ssis with multiple inputs
|
|
| sqlboy2000 2006-03-23, 8:35 pm |
| I'm using a script component in ssis to create some custom output columns
with vb.net. This is working great, and I've read that I can use mutiple
inputs to reuse the code with multiple data sources. However, when I create a
second source and try to drag a path to the script component, I get the
message that the component doesn't have any available inputs. When I edit the
transformation, I only see "Input 0" in the dropdown for input name. I can't
see any other way to create an additional input, and I'd hate to have to
include the vb.net code more than once in multiple script components in case
I have to change it. Does anyone know how to accomplish this?
Thanks in advance.
| |
| Darren Green 2006-03-24, 7:39 am |
| "When used as a transformation, the Script component supports one input and
multiple outputs."
http://msdn2.microsoft.com/en-us/library/ms135927.aspx
Do you really require multiple inputs or do you just require reuse of the
logic within the component on a second path? Either way you should consider a
custom managed component, as this allows you to create multiple inputs,
and/or offers reuse within the same package or accross packages.
--
http://wiki.sqlis.com | http://www.sqlis.com | http://www.sqldts.com
"sqlboy2000" wrote:
> I'm using a script component in ssis to create some custom output columns
> with vb.net. This is working great, and I've read that I can use mutiple
> inputs to reuse the code with multiple data sources. However, when I create a
> second source and try to drag a path to the script component, I get the
> message that the component doesn't have any available inputs. When I edit the
> transformation, I only see "Input 0" in the dropdown for input name. I can't
> see any other way to create an additional input, and I'd hate to have to
> include the vb.net code more than once in multiple script components in case
> I have to change it. Does anyone know how to accomplish this?
>
> Thanks in advance.
| |
| sqlboy2000 2006-03-24, 9:31 am |
| Ahh, thanks for the info.
"Darren Green" wrote:
[color=darkred]
> "When used as a transformation, the Script component supports one input and
> multiple outputs."
>
> http://msdn2.microsoft.com/en-us/library/ms135927.aspx
>
> Do you really require multiple inputs or do you just require reuse of the
> logic within the component on a second path? Either way you should consider a
> custom managed component, as this allows you to create multiple inputs,
> and/or offers reuse within the same package or accross packages.
>
> --
> http://wiki.sqlis.com | http://www.sqlis.com | http://www.sqldts.com
>
>
> "sqlboy2000" wrote:
>
|
|
|
|
|