Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
Author |
Topic |
AskSQLTeam
Ask SQLTeam Question
0 Posts |
Posted - 2005-11-11 : 07:29:16
|
Balamurugan writes "Hi,I have created a login in SQL Server 2000 for a business user and added him in the 'Processadmin' fixed server role. He needs to be trigger the SQL jobs manually.But there are no job have been listed in the enterprise manager while using his login.Kindly provide your suggestions.Bala" |
|
mcrowley
Aged Yak Warrior
771 Posts |
Posted - 2005-11-11 : 09:19:16
|
By default, I think any user can create a job, or run their own jobs. If the jobs are in fact there (visible by sysadmin), does the user own the jobs? |
 |
|
balancoats
Starting Member
5 Posts |
Posted - 2005-11-11 : 14:01:09
|
The job is schedule to run on behalf of a DTS Package. The package is owned by sysadmin. |
 |
|
mcrowley
Aged Yak Warrior
771 Posts |
Posted - 2005-11-11 : 15:02:59
|
You will have to change the ownership of the jobs. I think processadmins only get to kill other processes. They do not get much in the way of starting them, I think. |
 |
|
balancoats
Starting Member
5 Posts |
Posted - 2005-11-11 : 17:48:17
|
I have changed the ownership. Now the job have been listed for his login, but he is not able to execute the job.In job history, it shows that 'Non-SysAdmins have been denied permission to run CmdExec job steps'. |
 |
|
|
|
|