This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(278.4, 97%, 36%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ERK%3C/text%3E%3C/svg%3E)
auto sync of SQL logins and SQL jobs from primary to secondary in always on
Also can you suggest whether we could move the jobs created in primary can be moved to secondary?
You can script them in SSMS and then copy to the other server.
You will need to add something to prevent the job from running on the secondary. A common way is to have a first job step which attempts to access the database. Then you mark the step as "quit the job and report success" in case of an error. The second step of the job has the real action.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(124.80000000000001, 39%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ERK%3C/text%3E%3C/svg%3E)
The requirement is the job created in primary has to move to secondary automatically.
I googled auto sync of jobs in availability group sql server and I got some hits, although it seems that the hits are often related to sync logins, which is the easier part. But this Stackoverflow answer has a couple of links: https://dba.stackexchange.com/questions/292085/how-to-sync-logins-and-jobs-when-using-an-availability-group I did not watch this YouTube video, but the title is promising: https://www.youtube.com/watch?v=hRpLco6ysBo,
You should probably explore the search result yourself.
Hi @Rajesh Kumar,
You might find this article Synchronize logins between Availability replicas in SQL Server Always On Availability Groups helpful.
Depending on how many Secondary Replicas you are planning to setup, or if you have an affinity to SSIS, you might find it cleaner and more manageable to create an SSIS Package that does all of this (which is also discussed in the first article above) as opposed to using Linked Servers.
Regards，
Zoe Hui
If the answer is helpful, please click "Accept Answer" and upvote it.
Thanks for the response.
We are using SQL server 2016 standard edition with primary and secondary. we could create the SSIS for logins sync to secondary, also the requirement is for any role changed to login in primary also has to get sync .
Also can you suggest whether we could move the jobs created in primary can be moved to secondary?
If you are on SQL 2022, you can create a Contained Availability Group to relieve yourself from this problem.
We are using SQL 2016 standard edition