| You are not authorized to post a reply. |
|
| Author |
Messages |
|
SuperUser
 
Posts:26
 |
| 10/28/2005 11:54 AM |
|
| Has anyone gotten this agent to properly communicate with the SQL instances using "db_owner" or "db_datereader" security roles? In my testing this agent will not run is Run without Resource is connected using "sa". And that's a role that the DBAs do not want us to have. |
|
|
|
SuperUser
Posts:26
|
| 10/30/2005 5:10 PM |
|
| Part of the issue with this agent appears to be that contrary to Microsoft's belief that any other account in SQL can be given rights as or close to SA is pure bunk. I too had this fight with the DBA's and it appears that a number of the internal's the agent accesses are only available to SA. It does not seem to work even if you attempt to create a different account with all the rights of SA. I wish you luck dude... If you find a way to make it work with a service account, let us know. |
|
|
|
|
| You are not authorized to post a reply. |
|
|
|