Job step command box can hold only 3200 characters

I could not load a batch file into the command box of a job step because it
exceeded the 3200 character limit. How do I increase this limit?
Mucho gracias.
LaEsmeraldaUse another job step.
--
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"LaEsmeralda" <LaEsmeralda@.discussions.microsoft.com> wrote in message
news:B53AE718-D28F-473F-B347-D547D1072A2D@.microsoft.com...
>I could not load a batch file into the command box of a job step because it
> exceeded the 3200 character limit. How do I increase this limit?
> Mucho gracias.
> LaEsmeralda

Job step command box can hold only 3200 characters

I could not load a batch file into the command box of a job step because it
exceeded the 3200 character limit. How do I increase this limit?
Mucho gracias.
LaEsmeraldaUse another job step.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"LaEsmeralda" <LaEsmeralda@.discussions.microsoft.com> wrote in message
news:B53AE718-D28F-473F-B347-D547D1072A2D@.microsoft.com...
>I could not load a batch file into the command box of a job step because it
> exceeded the 3200 character limit. How do I increase this limit?
> Mucho gracias.
> LaEsmeraldasql

Job step command box can hold only 3200 characters

I could not load a batch file into the command box of a job step because it
exceeded the 3200 character limit. How do I increase this limit?
Mucho gracias.
LaEsmeralda
Use another job step.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"LaEsmeralda" <LaEsmeralda@.discussions.microsoft.com> wrote in message
news:B53AE718-D28F-473F-B347-D547D1072A2D@.microsoft.com...
>I could not load a batch file into the command box of a job step because it
> exceeded the 3200 character limit. How do I increase this limit?
> Mucho gracias.
> LaEsmeralda

Job schedule interval limits using Management Studio

Has anybody else seen the limit Management Studio's interface puts on the scheduling of jobs? Specifically, if the units is "minutes", the frequency can't be more than 60 (and similarly, the limit for "hours" is 24).

Thanks!

-dave

Yes, we've seen that. Is there a question?|||

Heh.. sorry. I guess the question/assumption is... that's a known bug and will be fixed at some point (?).

Thanks!

|||A bug would mean that it isn't working as designed. This isn't a bug. You can only configure 60 when you select minutes for a value, because there are only 60 minutes in an hour. You can only configure 24 for hours, because there are only 24 hours in a day. I'm not sure what you're trying to do.|||

Michael,

I can easily see times to have a JOB execute every 90 minutes, for example. The Current scheduling GUI doens't allow that without using 'creative' options.

More flexibility with the scheduling GUI would be an excellent move!

|||

Arnie beat me to it, but... yes, every 90 minutes is a good example.

FWIW, I ran into this while trying to implement Quest LiteSpeed's log shipping solution. Their l/s wizard adds a job with twice the l/s interval, which I'd set to 60 minutes. (Oddly enough, their own Enterprise Console front end won't let you put in more than 100 minutes... very strange). Trying to edit that job's schedule with Management Studio gives a popup error box and does not allow entry to the schedule (in effect: "the schedule has an error, but we're not letting you in to fix it").

Finally, this is yet ANOTHER instance of regression from 2000 to 2005, in that Enterprise Manager has no such limit.

|||MSDN Product Feedback Center. Post a suggestion. Then get a bunch of people to vote on including it. Yes, you do have the ability to directly influence feature requests.

Job History

Is there a limit to the number of rows that are stored in job history?
I see where the Maintenance Plan history can be set, but not for the
individual jobs. I have set up a test job and run it over 100 times, but
there seems to be a limit of 100 entries in the sysjobhistory table.
Is this correct and if it is, where is that documented?
Thanks,
Will
Never Mind - I see that the setting is in the SQL Server Agent properties.
"Will Winn" wrote:

> Is there a limit to the number of rows that are stored in job history?
> I see where the Maintenance Plan history can be set, but not for the
> individual jobs. I have set up a test job and run it over 100 times, but
> there seems to be a limit of 100 entries in the sysjobhistory table.
> Is this correct and if it is, where is that documented?
> Thanks,
> Will

Job History

Is there a limit to the number of rows that are stored in job history?
I see where the Maintenance Plan history can be set, but not for the
individual jobs. I have set up a test job and run it over 100 times, but
there seems to be a limit of 100 entries in the sysjobhistory table.
Is this correct and if it is, where is that documented?
Thanks,
WillNever Mind - I see that the setting is in the SQL Server Agent properties.
"Will Winn" wrote:

> Is there a limit to the number of rows that are stored in job history?
> I see where the Maintenance Plan history can be set, but not for the
> individual jobs. I have set up a test job and run it over 100 times, but
> there seems to be a limit of 100 entries in the sysjobhistory table.
> Is this correct and if it is, where is that documented?
> Thanks,
> Will

Job History

Is there a limit to the number of rows that are stored in job history?
I see where the Maintenance Plan history can be set, but not for the
individual jobs. I have set up a test job and run it over 100 times, but
there seems to be a limit of 100 entries in the sysjobhistory table.
Is this correct and if it is, where is that documented?
Thanks,
WillNever Mind - I see that the setting is in the SQL Server Agent properties.
"Will Winn" wrote:
> Is there a limit to the number of rows that are stored in job history?
> I see where the Maintenance Plan history can be set, but not for the
> individual jobs. I have set up a test job and run it over 100 times, but
> there seems to be a limit of 100 entries in the sysjobhistory table.
> Is this correct and if it is, where is that documented?
> Thanks,
> Will

job failed on resource limit

Hi,
I have a job that pulls data from a linked server into
this server's database. I am working on sql server 2000.
It generally runs fine, but twice it failed on this error
message: 'OLE DB provider 'SQLOLEDB' reported an error.
Execution terminated by the provider because a resource
limit was reached. [SQLSTATE 42000] (Error 7399)
[SQLSTATE 01000] (Error 7312) OLE DB error trace [OLE/DB
Provider 'SQLOLEDB' ICommandText::Execute returned
0x80040e31: Execution terminated by the provider because
a resource limit was reached.]. [SQLSTATE 01000] (Error
7300). The step failed.'
When it says resource limit was reached, was it
complaining the number of connections at the linked server
has reached the limit?
Many thanks.
JJIt generally means a timeout has been exceeded (that's what 0x80040e31
means). You can increase the timeout to try and prevent this issue.
--
HTH
Jasper Smith (SQL Server MVP)
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"JJ Wang" <jwang@.leapwireless.com> wrote in message
news:09b401c371e7$6f7330b0$a101280a@.phx.gbl...
Hi,
I have a job that pulls data from a linked server into
this server's database. I am working on sql server 2000.
It generally runs fine, but twice it failed on this error
message: 'OLE DB provider 'SQLOLEDB' reported an error.
Execution terminated by the provider because a resource
limit was reached. [SQLSTATE 42000] (Error 7399)
[SQLSTATE 01000] (Error 7312) OLE DB error trace [OLE/DB
Provider 'SQLOLEDB' ICommandText::Execute returned
0x80040e31: Execution terminated by the provider because
a resource limit was reached.]. [SQLSTATE 01000] (Error
7300). The step failed.'
When it says resource limit was reached, was it
complaining the number of connections at the linked server
has reached the limit?
Many thanks.
JJ|||thanks, Jasper. Where should I go to adjust the time-out?
JJ
>--Original Message--
>It generally means a timeout has been exceeded (that's
what 0x80040e31
>means). You can increase the timeout to try and prevent
this issue.
>--
>HTH
>Jasper Smith (SQL Server MVP)
>I support PASS - the definitive, global
>community for SQL Server professionals -
>http://www.sqlpass.org
>"JJ Wang" <jwang@.leapwireless.com> wrote in message
>news:09b401c371e7$6f7330b0$a101280a@.phx.gbl...
>Hi,
>I have a job that pulls data from a linked server into
>this server's database. I am working on sql server 2000.
>It generally runs fine, but twice it failed on this error
>message: 'OLE DB provider 'SQLOLEDB' reported an error.
>Execution terminated by the provider because a resource
>limit was reached. [SQLSTATE 42000] (Error 7399)
>[SQLSTATE 01000] (Error 7312) OLE DB error trace [OLE/DB
>Provider 'SQLOLEDB' ICommandText::Execute returned
>0x80040e31: Execution terminated by the provider because
>a resource limit was reached.]. [SQLSTATE 01000] (Error
>7300). The step failed.'
>When it says resource limit was reached, was it
>complaining the number of connections at the linked server
>has reached the limit?
>Many thanks.
>JJ
>
>.
>