DSXchange

Hi,

Suddenly I checked in all server jobs in all project has limits to stop stage set 50 instead of no limit.
Please give suggestion to set again for no limit.

Funny, my clients always ran theirs with a limit of 1, thousands of jobs over many years. There's no reason for a Server job to ever throw an error unless something is really wrong and it needs to stop. IMHO.

Now, how are you running them? Does it matter if they are started manually from the client side via Director or Designer or all these all scheduled or run via an Enterprise Scheduler or command like via a script or ... ?? Just trying to get a handle on where the limit might have gotten reset.

Also note that I am assuming you meant they stop after 50 warnings rather than 50 rows. Please correct any invalid assumptions on my part.

Server jobs can also be run with a row limit, looks like these have been set for the OP's project. The solution is to set these values to 0 ( = no limit ).

Parallel jobs can also be row limited if compiled in trace mode.