Lines in a job cmdexec step

Does it only execute the first line, or is there a way to have it
execute multiple lines? Sure seems like it just does one line. Seems
fine if that line executes a .cmd file with multiple lines.
But for some reasons I *thought* you could put multiple lines in the
little text window in the job editor and it would work, but it's not.
I'm trying to set a couple of environment variables before calling a
dts package:
--
set foo=123
dtsrun mypackage
--
Thanks.
Josh> Does it only execute the first line, or is there a way to have it
> execute multiple lines?
For cmdExec job steps, only the first line will be executed. Is using a bat file an option?
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"jxstern" <jxstern@.wherever.com> wrote in message news:q13v529cuemj7e79o2is9cfds5vncn4v8s@.4ax.com...
> Does it only execute the first line, or is there a way to have it
> execute multiple lines? Sure seems like it just does one line. Seems
> fine if that line executes a .cmd file with multiple lines.
> But for some reasons I *thought* you could put multiple lines in the
> little text window in the job editor and it would work, but it's not.
> I'm trying to set a couple of environment variables before calling a
> dts package:
> --
> set foo=123
> dtsrun mypackage
> --
>
> Thanks.
> Josh
>|||On Tue, 9 May 2006 15:11:47 +0200, "Tibor Karaszi"
<tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote:
>> Does it only execute the first line, or is there a way to have it
>> execute multiple lines?
>For cmdExec job steps, only the first line will be executed. Is using a bat file an option?
Guess so!
Already had them written, actually, for testing purposes.
Now have to run them through the deployment process ...
Thanks.
Josh

Lines in a job cmdexec step

Does it only execute the first line, or is there a way to have it
execute multiple lines? Sure seems like it just does one line. Seems
fine if that line executes a .cmd file with multiple lines.
But for some reasons I *thought* you could put multiple lines in the
little text window in the job editor and it would work, but it's not.
I'm trying to set a couple of environment variables before calling a
dts package:
set foo=123
dtsrun mypackage
--
Thanks.
Josh> Does it only execute the first line, or is there a way to have it
> execute multiple lines?
For cmdExec job steps, only the first line will be executed. Is using a bat
file an option?
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"jxstern" <jxstern@.wherever.com> wrote in message news:q13v529cuemj7e79o2is9cfds5vncn4v8s@.
4a
x.com...
> Does it only execute the first line, or is there a way to have it
> execute multiple lines? Sure seems like it just does one line. Seems
> fine if that line executes a .cmd file with multiple lines.
> But for some reasons I *thought* you could put multiple lines in the
> little text window in the job editor and it would work, but it's not.
> I'm trying to set a couple of environment variables before calling a
> dts package:
> --
> set foo=123
> dtsrun mypackage
> --
>
> Thanks.
> Josh
>|||On Tue, 9 May 2006 15:11:47 +0200, "Tibor Karaszi"
<tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote:

>For cmdExec job steps, only the first line will be executed. Is using a bat file an
option?
Guess so!
Already had them written, actually, for testing purposes.
Now have to run them through the deployment process ...
Thanks.
Josh

Limit the Amount of Time for each job

Is there away to place at the beginning of a SQL Server job step the maximum
of amount you would like this step to execute. If the job steps executes
greater than this amount kill the step and go to the next step.
Please help me with this issue.
Thanks,maximum amount of what?
"Joe K." wrote:

> Is there away to place at the beginning of a SQL Server job step the maxim
um
> of amount you would like this step to execute. If the job steps executes
> greater than this amount kill the step and go to the next step.
> Please help me with this issue.
> Thanks,
>|||Fix the step
"Joe K." <JoeK@.discussions.microsoft.com> wrote in message
news:6C8530C7-174C-4E05-88D0-90CA2AD4EF52@.microsoft.com...
> Is there away to place at the beginning of a SQL Server job step the
maximum
> of amount you would like this step to execute. If the job steps executes
> greater than this amount kill the step and go to the next step.
> Please help me with this issue.
> Thanks,
>

Limit the Amount of Time for each job

Is there away to place at the beginning of a SQL Server job step the maximum
of amount you would like this step to execute. If the job steps executes
greater than this amount kill the step and go to the next step.
Please help me with this issue.
Thanks,
maximum amount of what?
"Joe K." wrote:

> Is there away to place at the beginning of a SQL Server job step the maximum
> of amount you would like this step to execute. If the job steps executes
> greater than this amount kill the step and go to the next step.
> Please help me with this issue.
> Thanks,
>
|||Fix the step
"Joe K." <JoeK@.discussions.microsoft.com> wrote in message
news:6C8530C7-174C-4E05-88D0-90CA2AD4EF52@.microsoft.com...
> Is there away to place at the beginning of a SQL Server job step the
maximum
> of amount you would like this step to execute. If the job steps executes
> greater than this amount kill the step and go to the next step.
> Please help me with this issue.
> Thanks,
>

Limit the Amount of Time for each job

Is there away to place at the beginning of a SQL Server job step the maximum
of amount you would like this step to execute. If the job steps executes
greater than this amount kill the step and go to the next step.
Please help me with this issue.
Thanks,maximum amount of what?
"Joe K." wrote:
> Is there away to place at the beginning of a SQL Server job step the maximum
> of amount you would like this step to execute. If the job steps executes
> greater than this amount kill the step and go to the next step.
> Please help me with this issue.
> Thanks,
>|||Fix the step
"Joe K." <JoeK@.discussions.microsoft.com> wrote in message
news:6C8530C7-174C-4E05-88D0-90CA2AD4EF52@.microsoft.com...
> Is there away to place at the beginning of a SQL Server job step the
maximum
> of amount you would like this step to execute. If the job steps executes
> greater than this amount kill the step and go to the next step.
> Please help me with this issue.
> Thanks,
>