Share this PostProblem of the day: Transactional Replication was configured on a database in AlwaysOn Availability Group. When the group was failed over to synchronized secondary node Transactional Log Reader stopped working. Share this Post
Share this PostI had need other day to STOP and START all Distribution Push Agent. Using the syssubscriptions and syspublications I can easily build list of SQL commands to either stop or start all the Distribution Push Agents. With output to text, I can copy and execute from SQL Agent Job, or directly in SQL
Read More »
Share this PostI’ve been working with a customer to setup and test Merge Replication Publisher in AlwaysOn Availability Groups. To quickly spin up a test scenario, I used our Microsoft Azure AlwaysOn template for SQL Server 2014 and within a few minutes had a complete AlwaysOn Availability Groups environment with 2 SQL Server 2014 availability
Read More »
Share this PostShould the need arise, you can publish to a Transactional Replication subscriber alias provided you setup the subscriber using scripts and not SQL Server Management Studio Replication Wizard. First, verify client alias is configured to redirect connectivity to alias name. In example below SQL Server traffic to CHRISSK2012\SQL2K8_2 will be redirected to alias
Read More »
Share this PostTo improve SQL Distribution agent performance when applying Snapshot, first ZIP then copy the snapshot files locally to the subscriber. This is a great solution for subscribers on WAN international networks as ZIP can be smaller and faster to copy then Replication can move uncompressed Snapshot files. Testing shows a 1gb file can
Read More »