November 17, 2008 at 9:25 am
Our developers have noticed that when they connect to a SQL Server 2000 server through SQL Server 2005 Management Studio that they cannot see the jobs on the SQL Server 2000 server.
I've done some "googling" but haven't found much. Does anyone have a solution to allow read-only access to the jobs on the SQL 2000 Server from SQL 2005 Management Studio?
Thanks
November 17, 2008 at 9:44 am
give read-only access to msdb of sql 2000 and then tell user to connect using ssms 2005
November 17, 2008 at 9:46 am
TargetServersRole in msdb
Interesting choice of name hehehe This seems to of worked (Thanks RK). Developers can now see the jobs but can't add/update/delete.
Thanks
November 17, 2008 at 9:47 am
bang725 (11/17/2008)
give read-only access to msdb of sql 2000 and then tell user to connect using ssms 2005
hehehe that was my first thought too... but no dice.
TargetServersRole is the answer.
Thanks anyways
November 17, 2008 at 10:22 am
I've been working on getting our developers out of db_owner and this is one of the problems I've encountered. Even with them being a member of the TargetServersRole I can't get it to work. I get an error "A severe error occurred on the current command. The results, if any, should be discarded. (.Net SqlClient Data Provider)"
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply