SQLAgent Jobs Not Available after SP4 Applied
From: Jason Delaune (JasonDelaune_at_discussions.microsoft.com)
Date: 05/20/05
- Next message: Mike Epprecht \(SQL MVP\): "Re: SQLAgent Jobs Not Available after SP4 Applied"
- Previous message: TOMAS CARLOS OTANO: "Re: t-sql to drop database unconditionally"
- Next in thread: Mike Epprecht \(SQL MVP\): "Re: SQLAgent Jobs Not Available after SP4 Applied"
- Reply: Mike Epprecht \(SQL MVP\): "Re: SQLAgent Jobs Not Available after SP4 Applied"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Thu, 19 May 2005 16:22:02 -0700
Hello all,
I have created a generic user for our developers to use as the owner of the
SQL Server jobs they create. This way all developers can use a generic
account to manage the jobs they create so that all developers can easily see
each other jobs. For the jobs that required administrator access, we setup a
proxy account. This all worked great when our server was running SP3a.
We recently applied SP4 to the server and now we are receiving all kinds of
permission problems. Now when our developers what to see the jobs using the
generic account (job owner) they get errors about permissions denied to the
xp_sqlagent_* extended stored procedures as well as various other xp_*
extended stored procedures within the master database.
What has changed with SP4 that would cause this problem? And what's the easy
way to fix it other than making the generic account dbo within the master
database?
Thanks,
Jason
- Next message: Mike Epprecht \(SQL MVP\): "Re: SQLAgent Jobs Not Available after SP4 Applied"
- Previous message: TOMAS CARLOS OTANO: "Re: t-sql to drop database unconditionally"
- Next in thread: Mike Epprecht \(SQL MVP\): "Re: SQLAgent Jobs Not Available after SP4 Applied"
- Reply: Mike Epprecht \(SQL MVP\): "Re: SQLAgent Jobs Not Available after SP4 Applied"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
|