MS SQL Server Tools - Re: Unable to start JobManager thread for job

Author

Re: Unable to start JobManager thread for job

Mark

2005-05-31, 9:23 am

My mistake concerning the specific worker threads. two question areas:

1) what exactly do you mean concerning "as a result the job is
marked so it will not run again." Does this mean that if i setup the
job to retry, the issue will be resolved? If so, why?
2) should i make any changes to the default value for the TSQL
subsystem default worker threads or just drop in the new RAM and the
registry un-hacked?

thanks again for your help...

mark

Gert E.R. Drapers

2005-05-31, 8:24 pm

1) job schedules live inside the SQL Agent cache, once a job gets in a
situation where a thread can not be started that job will get disabled, so
until SQL Agent gets restarted, it will not get retried.

2) if the problem is memory, you can measure this using perfmon, you should
either add memory if you are not at 2GB VM size for SQL Agent or reduce the
number of worker threads. Each worker thread has a stack size of 1MB so you
can figure out how many threads you can run before exhausting the virtual
address space of SQL Agent.

GertD@SQLDev.Net

Please reply only to the newsgroups.
This posting is provided "AS IS" with no warranties, and confers no rights.
You assume all risk for your use.
Copyright © SQLDev.Net 1991-2005 All rights reserved.

"Mark" <mcook@sewsus.com> wrote in message
news:1117547048.277709.137840@f14g2000cwb.googlegroups.com...
> My mistake concerning the specific worker threads. two question areas:
>
> 1) what exactly do you mean concerning "as a result the job is
> marked so it will not run again." Does this mean that if i setup the
> job to retry, the issue will be resolved? If so, why?
> 2) should i make any changes to the default value for the TSQL
> subsystem default worker threads or just drop in the new RAM and the
> registry un-hacked?
>
> thanks again for your help...
>
> mark
>

Sponsored Links