Monday, March 26, 2012
running a job
to kick off another job. Will the job step wait 'till th
child job is completed before going to the next step?
TIADid you try it?
--
http://www.aspfaq.com/
(Reverse address to reply.)
"Jon Templar" <anonymous@.discussions.microsoft.com> wrote in message
news:733b01c4cc24$c209fd20$a301280a@.phx.gbl...
> I have a job with 3 steps. Each step has exec sp_start_job
> to kick off another job. Will the job step wait 'till th
> child job is completed before going to the next step?
> TIA|||When you call sp_start_job from another stored proc or an application, the
sp_start_job starts the job and the SQL in the calling SP or application does
not wait for the job to finish, it just keeps going.
I would expect the same behavior for when you exec sp_start_job in each of
the steps in your SQL Job.
To simulate long running jobs, you can use the WAITFOR command.
--e.g., wait for 10 minutes
waitfor DELAY '000:10:00'
Tea C.
"Jon Templar" wrote:
> I have a job with 3 steps. Each step has exec sp_start_job
> to kick off another job. Will the job step wait 'till th
> child job is completed before going to the next step?
> TIA
>
Friday, March 9, 2012
Run child package independently [FOUND IT]
I have a parent package which execute a child package. But when the child package is run from the parent not all of the tools inside is executed. I have a variable "ExecuteStep" from the parent that gives information about which tools, that needs to be executed.
BUT
The child package should be able to run independently also. In this case all tools inside the package should execute.
This is however not possible because my variable "ExecuteStep" does not exist inside the package, it is inheritage from my parent.
If I create a variable with exactly the same name inside my child package, I can run the child independently, but when executed from the parent the value from the parent package is now overwritten by the child variable.
How can I get around this problem?
bjarneThe solution was just in front of me all the time.
As "Package Configuration" I was using the XML file I had generated with the Parent variables.
Instead I should have been using "Parent package variable", this way all works fine.
I found it with a help from Kirk Haselden's blog
http://sqljunkies.com/WebLog/knight_reign/comments/5366.aspx
Bjarne
Run child package independently
I have a parent package which execute a child package. But when the child package is run from the parent not all of the tools inside is executed. I have a variable "ExecuteStep" from the parent that gives information about which tools, that needs to be executed.
BUT
The child package should be able to run independently also. In this case all tools inside the package should execute.
This is however not possible because my variable "ExecuteStep" does not exist inside the package, it is inheritage from my parent.
If I create a variable with exactly the same name inside my child package, I can run the child independently, but when executed from the parent the value from the parent package is now overwritten by the child variable.
How can I get around this problem?
bjarneThe solution was just in front of me all the time.
As "Package Configuration" I was using the XML file I had generated with the Parent variables.
Instead I should have been using "Parent package variable", this way all works fine.
I found it with a help from Kirk Haselden's blog
http://sqljunkies.com/WebLog/knight_reign/comments/5366.aspx
Bjarne