SQL Server Tips

Why Setting Up Right SQL Job Owner Matters?

Mark Varnas
1 comment

Users leave the organization.

When a login is disabled, deleted, or Active Directory is unavailable, the job may stop working.

The best practices recommend you set all SQL job owners to SA accounts.

Note: You might have a different approach, such as creating an account or login specifically for SQL Agent jobs.

How to verify the owner of all SQL Server Agent jobs?

You may use the query below to check the jobs and their owners:

SELECT sj.name AS [Job Name]
	,sj.[description] AS [Job Description]
	,SUSER_SNAME(sj.owner_sid) AS [Job Owner]
	,sj.date_created AS [Date Created]
	,sj.[enabled] AS [Job Enabled]
	,sc.name AS [Category Name]
FROM msdb.dbo.sysjobs AS sj WITH (NOLOCK)
INNER JOIN msdb.dbo.syscategories AS sc WITH (NOLOCK) ON sj.category_id = sc.category_id
ORDER BY sj.name
OPTION (RECOMPILE);

How to change SQL Server Agent jobs ownership?

  1. Using SSMS, click on Agent Server.
  2. Expand Jobs, right-click the Job Name, and select Properties.
  3. Change the property owner to SA.

More information

Article by
Mark Varnas
Founder | CEO | SQL Veteran
Hey, I'm Mark, one of the guys behind Red9. I make a living performance tuning SQL Servers and making them more stable. I channel my SQL into our SQL Managed Services, SQL Consulting and our internal database products.

1 thought on “Why Setting Up Right SQL Job Owner Matters?”

  1. Actually, it’s not best practice for the sa account to own jobs. That causes problems with SSIS jobs and the use of proxy accounts. You should test out creating a dummy SQL account–probably one without logon privileges and with at most a SQLAgentUserRole role–to own your jobs.

    Reply

Leave a Comment

Managed SQL Server services, consulting, and emergency support from expert DBAs to improve performance, predictability, and cost.

Get started with Red9 today.

Contact us

Discover More

Discover what clients are saying about Red9

Red9 has incredible expertise both in SQL migration and performance tuning.

The biggest benefit has been performance gains and tuning associated with migrating to AWS and a newer version of SQL Server with Always On clustering. Red9 was integral to this process. The deep knowledge of MSSQL and combined experience of Red9 have been a huge asset during a difficult migration. Red9 found inefficient indexes and performance bottlenecks that improved latency by over 400%.

Rich Staats 5 stars
Rich Staats
Cloud Engineer
MetalToad

Always willing to go an extra mile

Working with Red9 DBAs has been a pleasure. They are great team players and have an expert knowledge of SQL Server database administration. And are always willing to go the extra mile to get the project done.
5 stars
Evelyn A.
Sr. Database Administrator

Boosts server health and efficiency for enhanced customer satisfaction

Since adding Red9 to the reporting and DataWarehousing team, Red9 has done a good job coming up to speed on our environments and helping ensure we continue to meet our customer's needs. Red9 has taken ownership of our servers ensuring they remain healthy by monitoring and tuning inefficient queries.
5 stars
Andrew F.
Datawarehousing Manager
See more testimonials