Re: scheduling stored procedures to run as jobs

Fith wrote:
>
> Does anyone know why a procedure that runs from SQL+ (when executed
> manually) in around 38 minutes without affecting the processor much would
> max out the processor and take over 6 hours when scheduled as a job (through
> the enterprise manager)? I'm using version 7.3.3.
>
> Thanks.

You need to look at the execution plan while the sql is running each way.
It may be that the "optimizer goal" is different for the two sessions.

As to "maxing out" the processor, if you're running anything and it's not done yet something better be maxed out - usually either the processor or the disk drives.
Is your db server on unix or nt ? Received on Mon Apr 12 1999 - 19:06:18 CDT