![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
Hello, I have a DTS package that performs dozens of data pump tasks. I have set EACH data pump task up as going from one connection to another. This combination of task (con1 -> pumptask -> con2) is duplicated again and again within the package. I am using a dynamic properties task to change the connection but need to know if the workflow properties need to be set for EVERY data pump task to have a precedence of success of the Dynamic Properties task? If not, how do I choose which datapump task on which to set the workflow? Remember (for what its worth) that I have the package set up this way:- con1 -> pumptask1 -> con2 con1 -> pumptask2 -> con2 con1 -> pumptask3 -> con2 rather than -> pumptask1 con1 -> pumptask2 -> con2 -> pumptask3 Any ideas? |
#3
| |||
| |||
|
|
You don't The DataSource property is for the connection not a DataPump. In your example you have 2 connections only. -- -- Allan Mitchell MCSE,MCDBA, (Microsoft SQL Server MVP) www.SQLDTS.com - The site for all your DTS needs. www.konesans.com - Consultancy from the people who know "Andrew Grandison" <andrewgrandison (AT) hotmail (DOT) com> wrote in message news:1bf3229f.0408110113.31c96139 (AT) posting (DOT) google.com... Hello, I have a DTS package that performs dozens of data pump tasks. I have set EACH data pump task up as going from one connection to another. This combination of task (con1 -> pumptask -> con2) is duplicated again and again within the package. I am using a dynamic properties task to change the connection but need to know if the workflow properties need to be set for EVERY data pump task to have a precedence of success of the Dynamic Properties task? If not, how do I choose which datapump task on which to set the workflow? Remember (for what its worth) that I have the package set up this way:- con1 -> pumptask1 -> con2 con1 -> pumptask2 -> con2 con1 -> pumptask3 -> con2 rather than -> pumptask1 con1 -> pumptask2 -> con2 -> pumptask3 Any ideas? |
#4
| |||
| |||
|
|
True, but using the GUI (package designer) I can't set workflow properties for a connection - only for a data pump. I don't want to rely on a particular datapump task always being the first to execute and then linking the dynamic properties task to that task (via workflow/success). I must be missing something fundamental here because I can't find any posts providing info on what to do in this situation. Thanks "Allan Mitchell" <allan (AT) no-spam (DOT) sqldts.com> wrote You don't The DataSource property is for the connection not a DataPump. In your example you have 2 connections only. -- -- Allan Mitchell MCSE,MCDBA, (Microsoft SQL Server MVP) www.SQLDTS.com - The site for all your DTS needs. www.konesans.com - Consultancy from the people who know "Andrew Grandison" <andrewgrandison (AT) hotmail (DOT) com> wrote in message news:1bf3229f.0408110113.31c96139 (AT) posting (DOT) google.com... Hello, I have a DTS package that performs dozens of data pump tasks. I have set EACH data pump task up as going from one connection to another. This combination of task (con1 -> pumptask -> con2) is duplicated again and again within the package. I am using a dynamic properties task to change the connection but need to know if the workflow properties need to be set for EVERY data pump task to have a precedence of success of the Dynamic Properties task? If not, how do I choose which datapump task on which to set the workflow? Remember (for what its worth) that I have the package set up this way:- con1 -> pumptask1 -> con2 con1 -> pumptask2 -> con2 con1 -> pumptask3 -> con2 rather than -> pumptask1 con1 -> pumptask2 -> con2 -> pumptask3 Any ideas? |
![]() |
| Thread Tools | |
| Display Modes | |
| |