July 16, 2008 at 10:18 pm
I only have three SQL Logins with sysadmin rights on my server.
SA - which is disabled
SQLServer2005SQLAgentUser$COMPUTERNAME$MSSQLSERVER - local windows group
SQLServer2005MSSQLUser$COMPUTERNAME$MSSQLSERVER - local windows group
The local windows account for the SQL Service Agent is SQLAgent it belongs to the windows group SQLServer2005SQLAgentUser$COMPUTERNAME$MSSQLSERVER
The local windows account for the SQL Server Agent is SQLService it belongs to the windows group SQLServer2005MSSQLUser$COMPUTERNAME$MSSQLSERVER
I can't assign ownership to the jobs to a group. I can't assign ownership to SA because it is disabled. Should I create an explicit SQL Login for the SQL Agent Service account to own the jobs? This seems a little redundant because it is part of the group with sysadmin rights. Should I remove the local windows groups and just create SQL Logins for the SQL Agent and SQL Service accounts? What would be a recommended best practice?
July 16, 2008 at 11:33 pm
[font="Verdana"]You may change the owner of the job to SQL Agent service account? If your service is running on Localsystem then change the owner to NT AUTHORITY \ SYSTEM.
Through which ID are you connecting as sysadmin to sql server??[/font]
Regards..Vidhya Sagar
SQL-Articles
July 17, 2008 at 9:26 am
My sql agent account is a local windows account and I would like to keep it as such. How do I assign the job to that windows account? They do not exist within the drop down list of sql logins.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply