Monday, February 18, 2013 5:32 PM
Recently I found a number of databases listed as owned by a member of our team (domain\user). I changed the database owner to "sa". Then I started to wonder about our Sql Agent jobs......they were owned by the same user... so I changed those owners to "sa" and the jobs continue to run fine. then I checked the service account that the Agent runs under. It is listed as "Local service" which is all-powerful locally. But when I right-clicked (in SSMS) the SQL Agent and went to properties it showed the "connection" property as using the domain user name!
1. I guess, under these circumstances, I can change the "connection" property name to "sa" (as the jobs are being run by local service anyway). Does that make sense to you?
2. Also some SSIS jobs run under a proxy agent. I presume that that account preempts "local service" for those jobs so we are still safe changing the connection to "sa". Do you agree?
P.S. Given our IS Team generally logs into servers using their domain name (for auditing purposes) this leads quite naturally to the situation described above. We need to be diligent to change DB\SSIS owners to "sa" after they are created.
- Edited by edm2 Monday, February 18, 2013 6:14 PM
Wednesday, February 20, 2013 9:08 AMModerator
We use SQL Server Agent Properties (Connection Page) to view and modify the settings for the connection from the Microsoft SQL Server Agent service to SQL Server.
Do not select the Local Service account. The SQL Server Agent service cannot be run under this account. It is not supported. The name of this account is NT AUTHORITY\LocalService, and it accesses network resources as a null session with no credentials.
Selecting an Account for the SQL Server Agent Service: http://msdn.microsoft.com/en-us/library/ms191543(v=SQL.100).aspx.
TechNet Community Support
- Marked As Answer by Maggie LuoMicrosoft Contingent Staff, Moderator Tuesday, February 26, 2013 9:33 AM
Tuesday, February 26, 2013 9:33 AMModerator