I'm fairly new to SQL Server 2000 admin and DTS packages, and would
appreciate any help with the following problem.

We developed a DTS package to carry out various tasks, which ran fine from
the developer's PC. When the package was scheduled we got the error about
non-sysadmins being unable to run CmdExec. Looked through some stuff and
managed to find something on changing the owner of the job (as well as
creating a SQL agent proxy account). We changed the owner of the job to
'sa' and it now runs successfully at the scheduled time. However, the
developer can't see the job when they go to 'Jobs' in Enterprise Manager
(I'm assuming they won't be able to create or edit jobs either?). Can
anyone help out with assigning permissions to groups to allow
viewing/editing/creating scheduled tasks?

Also, can anyone point out the pros/cons with regards to setting the owner
of a scheduled job as opposed to using a proxy account? What is "best
practice"?

Thanks very much for any help you can give.

Liz Porteous
(e-mail: liz.porteous (AT) scottishfriendly (DOT) co.uk)

The abaility to create jobs is allowed to public. You have to have certain
perms to see jobs you do not own. Have a look at the TargetServers role in
MSDB.

--

Allan Mitchell (Microsoft SQL Server MVP)
MCSE,MCDBA
www.SQLDTS.com
I support PASS - the definitive, global community
for SQL Server professionals - http://www.sqlpass.org


"LizP(SFA)" <liz.porteous (AT) scottishfriendly (DOT) co.uk> wrote