|
|
You're in the
sql server dts
group:DTS package Precedence not working
sql server dts:
I have a master DTS package that is made up of multiple other DTS packages.
The process that we run nightly is something like: Step 1 (pull data) On Success Step 2 (aggregate data) On Success Step 3 (generate key in separate table) On Success Step 4 (push data into final table) It's important that the package come to a hault if something goes wrong in step 3 as we don't want records in the table (step 4) that don't have corresponding records in the key table. Hence we put a workflow step in between each execute dts package task saying move to the next step "on success". However in observing the package execute it seems to move the next step regardless of the results in the prior step. If step 3 fails step 4 starts going instead of aborting the master package? Wondering if this is a known issue? Any help would be greatly appreicated. I"m using SQL SERVER2k on a Win2k3 server. Thanks in advance.
I came to the forum to ask this exact same question. Sorry I can't help, but
just so ppl know that there are a few interested parties. [quoted text, click to view] "TCG_GILBERT" wrote:
> I have a master DTS package that is made up of multiple other DTS packages. > The process that we run nightly is something like: > Step 1 (pull data) > On Success > Step 2 (aggregate data) > On Success > Step 3 (generate key in separate table) > On Success > Step 4 (push data into final table) > > It's important that the package come to a hault if something goes wrong in > step 3 as we don't want records in the table (step 4) that don't have > corresponding records in the key table. Hence we put a workflow step in > between each execute dts package task saying move to the next step "on > success". However in observing the package execute it seems to move the next > step regardless of the results in the prior step. If step 3 fails step 4 > starts going instead of aborting the master package? > Wondering if this is a known issue? Any help would be greatly appreicated. > > I"m using SQL SERVER2k on a Win2k3 server. > Thanks in advance.
I noticed a check-box, in the Logging tab of the Package Properties, called
"Fail package on first error". Will ticking this box generate the desired behaviour? I will probably try to test this. [quoted text, click to view] "TCG_GILBERT" wrote:
> I have a master DTS package that is made up of multiple other DTS packages. > The process that we run nightly is something like: > Step 1 (pull data) > On Success > Step 2 (aggregate data) > On Success > Step 3 (generate key in separate table) > On Success > Step 4 (push data into final table) > > It's important that the package come to a hault if something goes wrong in > step 3 as we don't want records in the table (step 4) that don't have > corresponding records in the key table. Hence we put a workflow step in > between each execute dts package task saying move to the next step "on > success". However in observing the package execute it seems to move the next > step regardless of the results in the prior step. If step 3 fails step 4 > starts going instead of aborting the master package? > Wondering if this is a known issue? Any help would be greatly appreicated. > > I"m using SQL SERVER2k on a Win2k3 server. > Thanks in advance.
I believe this check box is to fail on error of writing the log. Not on error
of the dts package itself. [quoted text, click to view] "Les Russell" wrote:
> I noticed a check-box, in the Logging tab of the Package Properties, called > "Fail package on first error". Will ticking this box generate the desired > behaviour? I will probably try to test this. > > "TCG_GILBERT" wrote: > > > I have a master DTS package that is made up of multiple other DTS packages. > > The process that we run nightly is something like: > > Step 1 (pull data) > > On Success > > Step 2 (aggregate data) > > On Success > > Step 3 (generate key in separate table) > > On Success > > Step 4 (push data into final table) > > > > It's important that the package come to a hault if something goes wrong in > > step 3 as we don't want records in the table (step 4) that don't have > > corresponding records in the key table. Hence we put a workflow step in > > between each execute dts package task saying move to the next step "on > > success". However in observing the package execute it seems to move the next > > step regardless of the results in the prior step. If step 3 fails step 4 > > starts going instead of aborting the master package? > > Wondering if this is a known issue? Any help would be greatly appreicated. > > > > I"m using SQL SERVER2k on a Win2k3 server. > > Thanks in advance.
I checked through a bunch of other posts here, and found a couple which also
described this problem. Both were answered by a Darren Green who indicated that this check box will work. Have a look at the post dated 10/21/2004 entitled "Execute Package Task - Workflow". I will definitely test it now. [quoted text, click to view] "tcg_gilbert" wrote:
> I believe this check box is to fail on error of writing the log. Not on error > of the dts package itself. >
The fail on first error will mean the child stops on error, no on error
workflow will be followed, but more importantly for you this also means the error is bubbled up to the Exec Pkg Task in the parent and this task also then fails. -- Darren Green http://www.sqldts.com [quoted text, click to view] "Les Russell" <LesRussell@discussions.microsoft.com> wrote in message news:B70D8547-838C-4A42-8C17-68733A2E6BCA@microsoft.com... > I checked through a bunch of other posts here, and found a couple which also > described this problem. Both were answered by a Darren Green who indicated > that this check box will work. Have a look at the post dated 10/21/2004 > entitled "Execute Package Task - Workflow". > > I will definitely test it now. > > "tcg_gilbert" wrote: > > > I believe this check box is to fail on error of writing the log. Not on error > > of the dts package itself. > > >
Thanks for this Darren.
I guess that means that you cannot easily have a child process which both has on-error processing, but which you also want to signal a fail to a parent if any other tasks fail. Any clues as to how this could be done - ActiveX would be required I guess? [quoted text, click to view] "Darren Green" wrote:
> The fail on first error will mean the child stops on error, no on error > workflow will be followed, but more importantly for you this also means the > error is bubbled up to the Exec Pkg Task in the parent and this task also > then fails. > > > -- > Darren Green > http://www.sqldts.com > > "Les Russell" <LesRussell@discussions.microsoft.com> wrote in message > news:B70D8547-838C-4A42-8C17-68733A2E6BCA@microsoft.com... > > I checked through a bunch of other posts here, and found a couple which > also > > described this problem. Both were answered by a Darren Green who > indicated > > that this check box will work. Have a look at the post dated 10/21/2004 > > entitled "Execute Package Task - Workflow". > > > > I will definitely test it now. > > > > "tcg_gilbert" wrote: > > > > > I believe this check box is to fail on error of writing the log. Not on > error > > > of the dts package itself. > > > > > > >
Hey, thanks to each of you for the help.
I'll give it a shot tomorrow. Josh [quoted text, click to view] "TCG_GILBERT" wrote:
> I have a master DTS package that is made up of multiple other DTS packages. > The process that we run nightly is something like: > Step 1 (pull data) > On Success > Step 2 (aggregate data) > On Success > Step 3 (generate key in separate table) > On Success > Step 4 (push data into final table) > > It's important that the package come to a hault if something goes wrong in > step 3 as we don't want records in the table (step 4) that don't have > corresponding records in the key table. Hence we put a workflow step in > between each execute dts package task saying move to the next step "on > success". However in observing the package execute it seems to move the next > step regardless of the results in the prior step. If step 3 fails step 4 > starts going instead of aborting the master package? > Wondering if this is a known issue? Any help would be greatly appreicated. > > I"m using SQL SERVER2k on a Win2k3 server. > Thanks in advance.
Exactly. Bit of a trade off when using the Exec Pkg Task. The alternative
is to use another execution mechanism, such as doing it directly from ActiveX Script. -- Darren Green http://www.sqldts.com [quoted text, click to view] "Les Russell" <LesRussell@discussions.microsoft.com> wrote in message news:DE8767D0-C4DB-4262-BADD-3FFAB8B48629@microsoft.com... > Thanks for this Darren. > > I guess that means that you cannot easily have a child process which both > has on-error processing, but which you also want to signal a fail to a parent > if any other tasks fail. > > Any clues as to how this could be done - ActiveX would be required I guess? > > "Darren Green" wrote: > > > The fail on first error will mean the child stops on error, no on error > > workflow will be followed, but more importantly for you this also means the > > error is bubbled up to the Exec Pkg Task in the parent and this task also > > then fails. > > > > > > -- > > Darren Green > > http://www.sqldts.com > > > > "Les Russell" <LesRussell@discussions.microsoft.com> wrote in message > > news:B70D8547-838C-4A42-8C17-68733A2E6BCA@microsoft.com... > > > I checked through a bunch of other posts here, and found a couple which > > also > > > described this problem. Both were answered by a Darren Green who > > indicated > > > that this check box will work. Have a look at the post dated 10/21/2004 > > > entitled "Execute Package Task - Workflow". > > > > > > I will definitely test it now. > > > > > > "tcg_gilbert" wrote: > > > > > > > I believe this check box is to fail on error of writing the log. Not on > > error > > > > of the dts package itself. > > > > > > > > > > > > >
Thanks for all your help.
[quoted text, click to view] "Darren Green" wrote:
> Exactly. Bit of a trade off when using the Exec Pkg Task. The alternative > is to use another execution mechanism, such as doing it directly from > ActiveX Script. > > > -- > Darren Green > http://www.sqldts.com > > "Les Russell" <LesRussell@discussions.microsoft.com> wrote in message > news:DE8767D0-C4DB-4262-BADD-3FFAB8B48629@microsoft.com... > > Thanks for this Darren. > > > > I guess that means that you cannot easily have a child process which both > > has on-error processing, but which you also want to signal a fail to a > parent > > if any other tasks fail. > > > > Any clues as to how this could be done - ActiveX would be required I > guess? > >
Don't see what you're looking for? Try a search.
|
June 2003
July 2003
August 2003
September 2003
October 2003
November 2003
December 2003
January 2004
February 2004
March 2004
April 2004
May 2004
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
| home · blog · groups | Questions? Comments? Contact the dn |