The necessary things have already been setup , the question is what exactly needs to be tested, I have never looked at these aplicatins and now has been asked to...

The column avg_fragmentation seems to have pretty high values on few of the indexes on the databases more than 80 and I beleive I should be rebuilding the indexes for...

We have a diffferent machine which is used to schedule jobs ( not SQL serer agent) and looks like this process tries to get the various jobs that needs to...

Though it is sleeping ( not performing any operation) , I see that the CPU numbers and Physical I/O numbers are high so should I be worrried about it??

In the activity monitor...

I have tried that but was of no help...I also tried giving the grant permission in all the SP's for 'TragetServers Role', it didnt help either...I keep getting the same...

I cannot go with the following options:

If you can, make that owner jobowner, and you should be fine, but that user will be able to modify the job.

Another more dangerous...

I dont think we have subscription , however I will try to open a case and see what exactly the problem could be . By the way I am running...

Just when I thought it was working.....it stopped.

when I follow the above suggestions I get the same login......

When I give the 'TargetServersRole' all the GRANT access on the SP that...

Oh boy....finally.....The role 'TargetServerRole' on msdb had DENY access on the Stored procedures which will be used to start/stop/create a new schedule/change a schedule for the jobs.. once the GRANT...

One more thing ..when the user is assigned to the role 'TargetServersRole ' , he is not able to start /stop any job. I did look into permissions for...

Now I get a meesage saying that

The schedule was not attached to the specific job.The schedule owner and the Job owner must be the same or the operation...

I tried that ..but was of no help....anything else that I am missing..

Here is the thing. The user had the following roles assigned on msdb

@rolename = 'db_dtsadmin',

@rolename = 'db_dtsltduser',

@rolename = 'db_dtsoperator',

@rolename = 'db_owner',

@rolename = 'SQLAgentOperatorRole',

@rolename = 'TargetServersRole',

when I changed it to...

I have tried to duplicate the issue in the Test environment and the user was able to Start the job and schedule it. I am not sure why the user...