Activity overview
Latest activity by Jefrackoff
Your concern about synchronizing instance-level objects across Availability Group (AG) replicas is valid since AGs only replicate database-level changes and don't automatically handle logins, linked servers, or SQL Agent jobs. Possible Solutions:
SQL Server Agent Jobs & Scripts – You can create custom scripts to periodically sync logins, jobs, and linked servers between replicas.
PowerShell Automation – Using PowerShell scripts, you can detect new/updated instance-level objects and sync them automatically across all AG nodes.
Use an Existing Tool – There are third-party tools like Redgate SQL Compare or dbatools (PowerShell module) that can help automate the process.
Triggers on System Tables? – While using DDL triggers on sys.server_principals , msdb.dbo.sysjobs , etc., is an idea, it could add overhead and doesn’t always capture all changes effectively.
Distributed Transactions (If Required) – If cross-server transactions are a concern, Linked Server MSDTC transactions could be an option, but they come with performance considerations.
If you're looking for a customized SQL gaming experience, you might find GTA Mzansi interesting—it's a South African-themed GTA mod that brings a fresh perspective to open-world gaming, just like how AGs bring reliability to SQL environments! 🚀 Hope this helps, and let us know what approach you decide on! / comments
Your concern about synchronizing instance-level objects across Availability Group (AG) replicas is valid since AGs only replicate database-level changes and don't automatically handle logins, linke...