July 29, 2009 at 2:02 pm
Hi All,
Just wondering what the importance of dbo sp_sqlagent_refresh_job is?
Also, i noticed that in one of my systems, it is a 'user' stored procedure in MSDB, but in the other it is a system stored procedure. The 'user' one has 'public' rights given to it and the system one does not.
Does anyone know how/why this is occurring and what would happen if i removed public access to the 'user' one?
Thanks in advance
July 29, 2009 at 3:24 pm
It's a proc SQL Agent uses to refresh the jobs cache. So, it matters.
Not sure why you'd have a user-created version, unless some DBA built a custom version of it for some reason.
- Gus "GSquared", RSVP, OODA, MAP, NMVP, FAQ, SAT, SQL, DNA, RNA, UOI, IOU, AM, PM, AD, BC, BCE, USA, UN, CF, ROFL, LOL, ETC
Property of The Thread
"Nobody knows the age of the human race, but everyone agrees it's old enough to know better." - Anon
July 31, 2009 at 1:24 pm
Thanks, one more thing correct me if im wrong. If we remove 'public' access to it (revoke EXECUTE), it shouldn't affect the way SQL server uses it because our SQL account is still 'sa' and should have permissions to execute it if it needs to...correct?
July 31, 2009 at 1:39 pm
Shouldn't. Have an undo script that reapplies the permission if something blows up.
- Gus "GSquared", RSVP, OODA, MAP, NMVP, FAQ, SAT, SQL, DNA, RNA, UOI, IOU, AM, PM, AD, BC, BCE, USA, UN, CF, ROFL, LOL, ETC
Property of The Thread
"Nobody knows the age of the human race, but everyone agrees it's old enough to know better." - Anon
July 31, 2009 at 1:42 pm
Yep already have the 'backout' plan - thanks for the help.
Viewing 5 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply