Permissions and SQL Server Agent

  • Hello,

    Our SQL Server Agent runs under an account, SQLAccount. SQLAccount permission to a network drive - n:\ has changed. In order for SQL Server Agent job(s) to utilize the network credentials of SQLAccount, SQL Server Agent needs to be re-started.

    I was wondering if there is any other way to have SQL Server Agent job(s) to utilize the latest credentials of SQLAccount without re-starting SQL Server Agent.

    Thanks.

    +ive

  • Not that I know of.

  • changing permissions shouldnt require an agent restart, just a password change.

  • Thank you.

    Just as a FYI, I was wondering if there are any workarounds to not stop and start SQL Agent in case of password change. In other words, what is the SQL Agent trying to do on stopping and starting and if this task can be manually performed while online.

    +ive

  • Positive (12/28/2009)


    Thank you.

    Just as a FYI, I was wondering if there are any workarounds to not stop and start SQL Agent in case of password change. In other words, what is the SQL Agent trying to do on stopping and starting and if this task can be manually performed while online.

    +ive

    When you change password the agent will carry on working until it stops and tries to restart, at that point it wont start. So you could happily change the password and then wait until the next maintenance window to restart the agent. There are a couple of replication cleanup jobs that, if set to run under the SQL agent account, will start to fail as soon as the password changes as it makes a new connection each time the jobs run. Apart from that your fine to change the password when you feel like it

Viewing 5 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply