New Job Unable to Copy 200 Line Code Into Command Section

I have a SQL Server 2000 database, I created a new job but I am unable to
copy the 200 lines of code that I created into the command section of the job.
Is there away to expand the New Job Command section?
I cannot use another job step to resolve this issue because I have alot
variables and a cursor used in this job.
This problem is resolve in SQL Server 2005.
Please help me resolve this problem for SQL Server 2000.
Thank You,Joe K. wrote:
> I have a SQL Server 2000 database, I created a new job but I am unable to
> copy the 200 lines of code that I created into the command section of the job.
> Is there away to expand the New Job Command section?
> I cannot use another job step to resolve this issue because I have alot
> variables and a cursor used in this job.
> This problem is resolve in SQL Server 2005.
> Please help me resolve this problem for SQL Server 2000.
> Thank You,
>
200 lines of code in a single job step? That's just insane. Put that
code into a stored procedure, and then use a single EXEC statement in
the job step.
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||I fully agree with Tracy. If you, for some strange reason, don't want to do this, I believe the
limit is a bit higher at the TSQL level (i.e., the GUI is the limiting factor), so you could have
some more by using sp_add_jobstep.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Tracy McKibben" <tracy@.realsqlguy.com> wrote in message news:45BA5D73.3080102@.realsqlguy.com...
> Joe K. wrote:
>> I have a SQL Server 2000 database, I created a new job but I am unable to copy the 200 lines of
>> code that I created into the command section of the job.
>> Is there away to expand the New Job Command section? I cannot use another job step to resolve
>> this issue because I have alot variables and a cursor used in this job.
>> This problem is resolve in SQL Server 2005.
>> Please help me resolve this problem for SQL Server 2000.
>> Thank You,
>>
> 200 lines of code in a single job step? That's just insane. Put that code into a stored
> procedure, and then use a single EXEC statement in the job step.
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com

New Job Unable to Copy 200 Line Code Into Command Section

I have a SQL Server 2000 database, I created a new job but I am unable to
copy the 200 lines of code that I created into the command section of the job.
Is there away to expand the New Job Command section?
I cannot use another job step to resolve this issue because I have alot
variables and a cursor used in this job.
This problem is resolve in SQL Server 2005.
Please help me resolve this problem for SQL Server 2000.
Thank You,
Joe K. wrote:
> I have a SQL Server 2000 database, I created a new job but I am unable to
> copy the 200 lines of code that I created into the command section of the job.
> Is there away to expand the New Job Command section?
> I cannot use another job step to resolve this issue because I have alot
> variables and a cursor used in this job.
> This problem is resolve in SQL Server 2005.
> Please help me resolve this problem for SQL Server 2000.
> Thank You,
>
200 lines of code in a single job step? That's just insane. Put that
code into a stored procedure, and then use a single EXEC statement in
the job step.
Tracy McKibben
MCDBA
http://www.realsqlguy.com

New Job Unable to Copy 200 Line Code Into Command Section

I have a SQL Server 2000 database, I created a new job but I am unable to
copy the 200 lines of code that I created into the command section of the jo
b.
Is there away to expand the New Job Command section?
I cannot use another job step to resolve this issue because I have alot
variables and a cursor used in this job.
This problem is resolve in SQL Server 2005.
Please help me resolve this problem for SQL Server 2000.
Thank You,Joe K. wrote:
> I have a SQL Server 2000 database, I created a new job but I am unable to
> copy the 200 lines of code that I created into the command section of the
job.
> Is there away to expand the New Job Command section?
> I cannot use another job step to resolve this issue because I have alot
> variables and a cursor used in this job.
> This problem is resolve in SQL Server 2005.
> Please help me resolve this problem for SQL Server 2000.
> Thank You,
>
200 lines of code in a single job step? That's just insane. Put that
code into a stored procedure, and then use a single EXEC statement in
the job step.
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||I fully agree with Tracy. If you, for some strange reason, don't want to do
this, I believe the
limit is a bit higher at the TSQL level (i.e., the GUI is the limiting facto
r), so you could have
some more by using sp_add_jobstep.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Tracy McKibben" <tracy@.realsqlguy.com> wrote in message news:45BA5D73.3080102@.realsqlguy.co
m...
> Joe K. wrote:
> 200 lines of code in a single job step? That's just insane. Put that c
ode into a stored
> procedure, and then use a single EXEC statement in the job step.
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com