August 3, 2023 at 10:58 pm
We have 3 nodes in Availability group so we have SQL agent jobs and there run times get changed accordingly on primary server only and it get's overlooked on other 2 nodes due to different reasons. Checking to see is there a way to ensure or setup an alert when the Job scheduling is not matching with all other nodes in AG group? Please advise?
August 4, 2023 at 4:56 pm
Probably the best way to handle that is to use the functionality built into SQL Server agent to manage a multi-server environment.
Ideally, you would use a server outside the AG as the master agent - and set each node in the AG as a target server. Then - when you add/edit/delete agent jobs in the master, the jobs will be updated on each target. This allows you to manage the agent jobs that need to be available on all nodes in a single place.
Using this configuration - you still have the ability to create and manage local agent jobs on each target. The local agent jobs would be those types of jobs that are specific to the instance.
Jeffrey Williams
“We are all faced with a series of great opportunities brilliantly disguised as impossible situations.”
― Charles R. Swindoll
How to post questions to get better answers faster
Managing Transaction Logs
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply