Long Running SQL Job

is there any contention while this sp is running as a job?
--
Venkat
sql server admirer
"FreeFish" wrote:

> I've got a SQL SP that when executed in QA takes 5 minutes to run, but whe
n
> scheduled as a Job, takes 35 minutes. Can anyone offer an explanation as
to
> why the difference?Nothing in particular. It would be the same as when I run in QA.
"Venkat" wrote:
[vbcol=seagreen]
> is there any contention while this sp is running as a job?
> --
> Venkat
> sql server admirer
>
> "FreeFish" wrote:
>|||I found it: SET NOCOUNT ON
Found this in a previous post on the same topic.
Thanks -
"FreeFish" wrote:
[vbcol=seagreen]
> Nothing in particular. It would be the same as when I run in QA.
> "Venkat" wrote:
>|||I've got a SQL SP that when executed in QA takes 5 minutes to run, but when
scheduled as a Job, takes 35 minutes. Can anyone offer an explanation as to
why the difference?|||is there any contention while this sp is running as a job?
--
Venkat
sql server admirer
"FreeFish" wrote:

> I've got a SQL SP that when executed in QA takes 5 minutes to run, but whe
n
> scheduled as a Job, takes 35 minutes. Can anyone offer an explanation as
to
> why the difference?|||Nothing in particular. It would be the same as when I run in QA.
"Venkat" wrote:
[vbcol=seagreen]
> is there any contention while this sp is running as a job?
> --
> Venkat
> sql server admirer
>
> "FreeFish" wrote:
>|||I found it: SET NOCOUNT ON
Found this in a previous post on the same topic.
Thanks -
"FreeFish" wrote:
[vbcol=seagreen]
> Nothing in particular. It would be the same as when I run in QA.
> "Venkat" wrote:
>