Job Sequencing ?

I have a job that runs a batch file, tsql step, and then another batch file.
My question is will the agent say the first step is complete and move on
when it starts the batch file or will it know to wait until after the batch
has ran to start the second step?
TIA
--
nivekHi
It waits for the prior step to finish.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"nivek" <eckart_612@.hotmail.com> wrote in message
news:36GdnYIXz77QzN3fRVn-3A@.centurytel.net...
> I have a job that runs a batch file, tsql step, and then another batch
file.
> My question is will the agent say the first step is complete and move on
> when it starts the batch file or will it know to wait until after the
batch
> has ran to start the second step?
> TIA
> --
> nivek
>
>
>

Job Sequencing ?

I have a job that runs a batch file, tsql step, and then another batch file.
My question is will the agent say the first step is complete and move on
when it starts the batch file or will it know to wait until after the batch
has ran to start the second step?
TIA
nivekHi
It waits for the prior step to finish.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"nivek" <eckart_612@.hotmail.com> wrote in message
news:36GdnYIXz77QzN3fRVn-3A@.centurytel.net...
> I have a job that runs a batch file, tsql step, and then another batch
file.
> My question is will the agent say the first step is complete and move on
> when it starts the batch file or will it know to wait until after the
batch
> has ran to start the second step?
> TIA
> --
> nivek
>
>
>

Job Sequencing ?

I have a job that runs a batch file, tsql step, and then another batch file.
My question is will the agent say the first step is complete and move on
when it starts the batch file or will it know to wait until after the batch
has ran to start the second step?
TIA
nivek
Hi
It waits for the prior step to finish.
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"nivek" <eckart_612@.hotmail.com> wrote in message
news:36GdnYIXz77QzN3fRVn-3A@.centurytel.net...
> I have a job that runs a batch file, tsql step, and then another batch
file.
> My question is will the agent say the first step is complete and move on
> when it starts the batch file or will it know to wait until after the
batch
> has ran to start the second step?
> TIA
> --
> nivek
>
>
>
sql

Job Scheduler

Hi all
When I run a stored procedure using the job scheduler in
SQL 2000 it takes more time to complete comparing when I
run it in the Query analyser.
Is there any reason behind this?
Example
I am running a stored Procedure for generating a report
every one minute using a job scheduler.
It takes 13 seconds to complete.
Whereas when I run the same SP in Query Analyser it takes
only 2 sec or 3 seconds.
Please clarify.
Thanks in advance
AnandThis could be the problem:
http://support.microsoft.com/defaul...730&Product=sql
--
HTH,
Vyas, MVP (SQL Server)
http://vyaskn.tripod.com/
Is .NET important for a database professional?
http://vyaskn.tripod.com/poll.htm
"Anand" <gurusanand@.yahoo.com> wrote in message
news:024101c3db49$baff3990$a001280a@.phx.gbl...
Hi all
When I run a stored procedure using the job scheduler in
SQL 2000 it takes more time to complete comparing when I
run it in the Query analyser.
Is there any reason behind this?
Example
I am running a stored Procedure for generating a report
every one minute using a job scheduler.
It takes 13 seconds to complete.
Whereas when I run the same SP in Query Analyser it takes
only 2 sec or 3 seconds.
Please clarify.
Thanks in advance
Anand

Job Scheduler

Hi all
When I run a stored procedure using the job scheduler in
SQL 2000 it takes more time to complete comparing when I
run it in the Query analyser.
Is there any reason behind this?
Example
I am running a stored Procedure for generating a report
every one minute using a job scheduler.
It takes 13 seconds to complete.
Whereas when I run the same SP in Query Analyser it takes
only 2 sec or 3 seconds.
Please clarify.
Thanks in advance
AnandThis could be the problem:
http://support.microsoft.com/default.aspx?scid=kb;en-us;249730&Product=sql
--
HTH,
Vyas, MVP (SQL Server)
http://vyaskn.tripod.com/
Is .NET important for a database professional?
http://vyaskn.tripod.com/poll.htm
"Anand" <gurusanand@.yahoo.com> wrote in message
news:024101c3db49$baff3990$a001280a@.phx.gbl...
Hi all
When I run a stored procedure using the job scheduler in
SQL 2000 it takes more time to complete comparing when I
run it in the Query analyser.
Is there any reason behind this?
Example
I am running a stored Procedure for generating a report
every one minute using a job scheduler.
It takes 13 seconds to complete.
Whereas when I run the same SP in Query Analyser it takes
only 2 sec or 3 seconds.
Please clarify.
Thanks in advance
Anand|||Do you SET NOCOUNT ON at the beginning of your stored
procedure? Sometimes this can help with this type of
problem.
Matthew Bando
BandoM@.CSCTGI(remove this).com
>--Original Message--
>Hi all
>When I run a stored procedure using the job scheduler in
>SQL 2000 it takes more time to complete comparing when I
>run it in the Query analyser.
>Is there any reason behind this?
>Example
>I am running a stored Procedure for generating a report
>every one minute using a job scheduler.
>It takes 13 seconds to complete.
>Whereas when I run the same SP in Query Analyser it
takes
>only 2 sec or 3 seconds.
>Please clarify.
>Thanks in advance
>Anand
>.
>

job runs OK without schedule, does not complete with schedule

I have a multistep job that has been working fine until recently, but for
some reason the server rebooted (power outage?) and ever since then the job
scheduler is not working as it should. The job starts, the 1st step
executes OK, but progress is not made to the next step and the job continues
to be in Execute mode.
...to work around this problem, I've disabled my job and have created 1 job
for each of the steps in my 'hanging' job. These smaller jobs run OK if I
don't attach a schedule to them, however, once I attach a schedule to each
job, the same problem recurs...the job completes OK, but the status of the
job remains Executing and never completes.
TIA for any suggestions and thoughts on this matter.I had a similar problem recently that was only resolved by re-installing the latest MDAC.|||Yes...that was it. Thank you very much.
"AC" <anonymous@.discussions.microsoft.com> wrote in message
news:DE5EBE1B-2562-4541-851A-3710A138E593@.microsoft.com...
> I had a similar problem recently that was only resolved by re-installing
the latest MDAC.sql