Re: SQL 2000 view current job status best practice
- From: "Jasper Smith" <jasper_smith9@xxxxxxxxxxx>
- Date: Wed, 11 Oct 2006 22:53:02 +0100
The TargetServer role doesn't let you see the current status of a job you
don't own however. There's no way to do that in EM unless you're a sysadmin.
It will however allow them to view the job history and job Properties but
not midify them.
--
HTH,
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
"Sue Hoegemeier" <Sue_H@xxxxxxxxxxxxx> wrote in message
news:odoqi2tsvvhficdgt533agtognr9e6cnf1@xxxxxxxxxx
Your asking for something that isn't doable in SQL Server
2000. The functionality in Enterprise Manager is built-in
and you can't really change that. The only other unsupported
way to do this would be to add the users to the TargetServer
role in msdb. Keep in mind that the role is undocumented
and using this is unsupported.
-Sue
On Wed, 11 Oct 2006 14:03:02 -0700, Richard Cote
<RichardCote@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
Sorry, I should have clarified this at the beginning. I am looking for a
solution to make the job status viewable from within SQL Enterprise
Manager.
"Warren Brunk" wrote:
There are a thousand different ways to implement this but here are the
basics.
I would create a stored procedure with something like this...
Create Procedure usp_runningjobs_s
as
begin
SELECT
sysp.cpu ,
sysp.spid,
sysp.status,
sysp.hostname,
sysp.program_name,
sysp.cmd,
sysp.cpu,
sysp.physical_io,
convert(sysname, rtrim(sysp.loginame)) as loginname,
sysp.spid as 'spid_sort',
substring( convert(varchar,sysp.last_batch,111) ,6 ,5 ) + ' ' +
substring( convert(varchar,sysp.last_batch,113) ,13 ,8 ) as
'last_batch_char'
from master.dbo.sysprocesses sysp (nolock)
inner join master.dbo.sysdatabases sysd (nolock)
on sysp.dbid = sysd.dbid
end
Then what you could do is grant permissions to execute the procedure to
the
users that you need. Or, even better is create a little .net webpage
that
calls this procedure and returns the results to a gridview.
What do you think?
--
/*
Warren Brunk - MCITP - SQL 2005, MCDBA
www.techintsolutions.com
*/
"Richard Cote" <RichardCote@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:F4DCBDD9-7A0F-4F7E-8F21-868AEF7BCCFF@xxxxxxxxxxxxxxxx
We have application support personnel who need to view the current
status
of
jobs running on production SQL 2000 (SP4) Servers. The application
support
group has very limited access to these production servers - such that
they
do
not have enough permissions to execute these jobs. Therefore,
changing
the
job owner is not a viable option. What is the best way to:
- allow the support personnel to view the status of jobs
- not increasing the account permissions within the databases
.
- Follow-Ups:
- Re: SQL 2000 view current job status best practice
- From: Sue Hoegemeier
- Re: SQL 2000 view current job status best practice
- References:
- Re: SQL 2000 view current job status best practice
- From: Warren Brunk
- Re: SQL 2000 view current job status best practice
- From: Richard Cote
- Re: SQL 2000 view current job status best practice
- From: Sue Hoegemeier
- Re: SQL 2000 view current job status best practice
- Prev by Date: Re: SQL Server Authentication
- Next by Date: Re: SQL 2000 view current job status best practice
- Previous by thread: Re: SQL 2000 view current job status best practice
- Next by thread: Re: SQL 2000 view current job status best practice
- Index(es):
Relevant Pages
|
