You have a couple or more SQL Servers with some sort of High Availability solution between them (Always On Availability Groups, Database Mirroring, etc.). You also have a bunch of scheduled jobs which you need to be run on the Primary server.

But wait…. How would you make these jobs run only on the Primary server? After all, if they try to run on the Secondary, they might fail (whether because the database is inaccessible or because it’s read-only). Additionally, you would need to consider a failover where the Primary and Secondary servers would switch roles.

This means that you would have to create these jobs on both servers, and then implement some sort of mechanism that would detect, for each job, whether the instance it’s being executed at is currently the Primary.

There are a few ways to go about doing this. During this session we will cover possible solutions, downfalls, tricks, and much more.

Presented by Eitan Blumin | Senior SQL Server Consultant and Team Leader | Madeira Data Solutions 

Eitan Blumin is a SQL Server Professional Generalist with decades of experience in all fields relating to Microsoft SQL Server databases (since the year 2005), including but not limited to: Database design, management, TSQL programming, performance tuning, replication, backup management, security management, high availability and disaster recovery, SSIS, SSRS, encryption and more. Other than his day-to-day consultant work, he also co-hosts the popular "SQL Server Radio" podcast with Guy Glantser, writes professional materials for the SQL Server community, delivers professional presentations and courses, and serves as a pivotal source of expert knowledge for the Madeira team.