March 3, 2004 at 2:09 am
Hour DBA's turned up security on our SQL Server environment and now we can still start our jobs, we can view job history but the status column of the jobs isn't updated anymore. As we have a number of jobs that have to be run each week it is important for us to see if the job started, finished or even failed. Can anyone tell me what we must change (as little as possible) in order to see the jobstatus updated again?
Regards,
Ivo Vink
March 3, 2004 at 2:52 am
http://www.sqlservercentral.com/forums/shwmessage.aspx?forumid=6&messageid=103131 offers some workarounds
--
Frank Kalis
Microsoft SQL Server MVP
Webmaster: http://www.insidesql.org/blogs
My blog: http://www.insidesql.org/blogs/frankkalis/[/url]
March 3, 2004 at 3:01 am
Frank,
Thanks for your quick response but regretfully this does not completely satisfy my question. The problem is that we do want to enable the starting and stopping of jobs. (and we can) but for some reason we can't see if the job is really running. Setting "TargetServersRole" revokes the right to start a job and that is not what we want.
The problem is that our DBA is actually a Oracle DBA and he does not know what he did wrong.
Ivo
March 3, 2004 at 3:11 am
Sorry, what about exec msdb..sp_help_jobhistory?
This s_proc is documented in BOL along with the description of the system table sysjobhistory. INformation on the table you'll find under jobs -> information stored in system table
HTH
--
Frank Kalis
Microsoft SQL Server MVP
Webmaster: http://www.insidesql.org/blogs
My blog: http://www.insidesql.org/blogs/frankkalis/[/url]
March 3, 2004 at 3:28 am
Frank,
That will certainly work! In the same way, we can just grafically check the jobhository. However, I still think it's strange that the status in the view isn't updated. There are some ways to work around the problem, and you mentioned some of them, but what I really wish to do is correct the problem and not the result.
If you can tell me what security feature inhibits my seeing the status change in the JobViewColumn I would be much obliged.
Ivo
March 3, 2004 at 3:57 am
From this point on, I would only be guessing and I don't want to do this.
Sorry, but I'm sure someone else will jump right in.
--
Frank Kalis
Microsoft SQL Server MVP
Webmaster: http://www.insidesql.org/blogs
My blog: http://www.insidesql.org/blogs/frankkalis/[/url]
March 3, 2004 at 4:03 am
I hope. In any way, thanks a lot for your efforts so far!!!
March 4, 2004 at 6:08 am
I remember spending a lot of time trying to figure this one out last year. Eventually a guy that I worked with who was "in the know" told me that you can't do it, even by assigning extra permissions to the users. He was trying to script a com object for users to be able to execute jobs and show their status and had done some serious research into pulling the job status and came to the conclusion that it cannot be done. Ultimately he created it with the user having to press a refresh button to see if the job was complete.
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply