Problem with ExpireExecutionLogEntries

Can anyone tell me what I could/should do to stop this stored proc from
running. It has been running all day and consuming resources. I've tried
killing the SPID and it just returns. We've stopped and started the SQL
Server service and its there here. Absent rebooting is there anything else
we should be doing. Also, can someone shed some light on why this rogue
process has started. We've been running Reporting Services SP1 for months
now and RS overall since early last year. This is the first problem we've
had. We currently going to SP2. Does SP2 address this issue.
Regards,
Eric FrayerThere must be a SQL job running this procedure. I very much doubt this
has anything to do with RS.
To try and locate the job, in query analyser logon to the msdb database
and run the following script;
SELECT j.job_id, j.name, j.description,
s.step_id, s.step_name, s.command
FROM sysjobsteps s
JOIN sysjobs j ON s.job_id = j.job_id
WHERE s.command LIKE '%MyProcName%'
Then you can investigate whatever the job is and what to do about it.
Chris
EFrayer@.community.nospam wrote:
> Can anyone tell me what I could/should do to stop this stored proc
> from running. It has been running all day and consuming resources.
> I've tried killing the SPID and it just returns. We've stopped and
> started the SQL Server service and its there here. Absent rebooting
> is there anything else we should be doing. Also, can someone shed
> some light on why this rogue process has started. We've been running
> Reporting Services SP1 for months now and RS overall since early last
> year. This is the first problem we've had. We currently going to
> SP2. Does SP2 address this issue. Regards,
> Eric Frayer|||Hi Chris,
Thanks for the reply. We stopped and started the SQL Service on the server
hosting the Reporting Services db's and this seemed to clear up the problem.
Regards,
Eric
"Chris McGuigan" wrote:
> There must be a SQL job running this procedure. I very much doubt this
> has anything to do with RS.
> To try and locate the job, in query analyser logon to the msdb database
> and run the following script;
> SELECT j.job_id, j.name, j.description,
> s.step_id, s.step_name, s.command
> FROM sysjobsteps s
> JOIN sysjobs j ON s.job_id = j.job_id
> WHERE s.command LIKE '%MyProcName%'
> Then you can investigate whatever the job is and what to do about it.
> Chris
>
> EFrayer@.community.nospam wrote:
> > Can anyone tell me what I could/should do to stop this stored proc
> > from running. It has been running all day and consuming resources.
> > I've tried killing the SPID and it just returns. We've stopped and
> > started the SQL Server service and its there here. Absent rebooting
> > is there anything else we should be doing. Also, can someone shed
> > some light on why this rogue process has started. We've been running
> > Reporting Services SP1 for months now and RS overall since early last
> > year. This is the first problem we've had. We currently going to
> > SP2. Does SP2 address this issue. Regards,
> > Eric Frayer
>