﻿<?xml version="1.0" encoding="utf-8"?><rss xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" version="2.0"><channel><title>SQLServerCentral.com Articles tagged Replication</title><link>http://www.sqlservercentral.com/</link><description>Articles tagged Replication posted on SQLServerCentral.com</description><language>en-us</language><ttl>360</ttl><managingEditor>sjones@sqlservercentral.com (Steve Jones)</managingEditor><item><title>High IO Wait on SQL Server Replication Distribution Database </title><description><![CDATA[<p>Have you ever heard this question? The database refresh has gone from 10-15 minutes to 1.5 hours. Nothing has changed on the application server and the consultant said ask the DBAs to check the database server. Where do you start to find the problem?  Check out this tip to learn more.</p>]]></description><guid>http://www.sqlservercentral.com/redirect/articles/99500/</guid><pubDate>Tue, 04 Jun 2013 06:00:00 UT</pubDate><link>http://www.sqlservercentral.com/redirect/articles/99500/</link></item><item><title>Super Fast Transactional Replication Repair</title><description><![CDATA[<p>Your production SQL Server transactional replication just failed and the business impact is critical. How do you get replication restored in minutes?</p><!-- disturbing m1(DBA Bundle) -->
<table border="0" cellpadding="0" cellspacing="10" style="width: 100%;"> <colgroup>  <col width="68" />  <col width="1266" /> </colgroup> <tbody>  <tr align="left" valign="top">   <td>    <a href="http://www.red-gate.com/products/dba/dba-bundle/entrypage/hard-earned-lessons-4?utm_source=ssc&utm_medium=pubad&utm_content=disturbing_m1&utm_campaign=sqldbabundle&utm_term=rss-20232"><img src="http://assets.red-gate.com/external/SSC/top5_68x68.gif" alt="sqldbabundle"></td>   <td><strong>‘Disturbing Development’</strong><br />Grant Fritchey & the DBA Team present the latest installment of the Top 5 hard-earned lessons of a DBA –  <a href="http://www.red-gate.com/products/dba/dba-bundle/entrypage/hard-earned-lessons-4?utm_source=ssc&utm_medium=pubad&utm_content=disturbing_m1&utm_campaign=sqldbabundle&utm_term=rss-20232">read it now</a></td>  </tr> </tbody></table>



]]></description><guid>http://www.sqlservercentral.com/articles/Replication/98897/</guid><pubDate>Thu, 30 May 2013 06:00:00 UT</pubDate><link>http://www.sqlservercentral.com/articles/Replication/98897/</link></item><item><title>Populating a Vertically Filtered Replicated Table</title><description><![CDATA[<p>Vertical filtering of a large replicated table introduces the potential for unwanted transactions to be pushed to the subscriber. This article talks about how you might avoid this.</p>]]></description><guid>http://www.sqlservercentral.com/articles/Replication/97230/</guid><pubDate>Wed, 20 Mar 2013 06:00:00 UT</pubDate><link>http://www.sqlservercentral.com/articles/Replication/97230/</link></item><item><title>Expanding AlwaysOn Availability Groups with Replication Publishers</title><description><![CDATA[<p>SQL Server 2012 AlwaysOn Availability Groups provide a high-availability and disaster-recovery solution for you SQL Server 2012 environments. Replication has been around in SQL Server for quite some time and allows you to scale out your environment. Warwick Rudd explains how to join these technologies together. </p>]]></description><guid>http://www.sqlservercentral.com/redirect/articles/96788/</guid><pubDate>Tue, 12 Feb 2013 07:00:00 UT</pubDate><link>http://www.sqlservercentral.com/redirect/articles/96788/</link></item><item><title>Stairway to SQL Server Replication: Level 1 - Introduction to SQL Server Replication</title><description><![CDATA[<p>In this Stairway, Sebastian will be covering the details of SQL Server transactional and merge replication, from understanding the basic terminology and methodology of setting up replication, to describing how it works and how the basic replication processes can be monitored. </p>]]></description><guid>http://www.sqlservercentral.com/articles/Stairway+Series/72274/</guid><pubDate>Wed, 26 Dec 2012 07:00:00 UT</pubDate><link>http://www.sqlservercentral.com/articles/Stairway+Series/72274/</link></item><item><title>Disaster In The Real World - #2</title><description><![CDATA[<p>Back in April Steve Jones wrote up a disaster at work. Andy had one this week and wrote up the story too. Copy cat! Pretty soon everyone will be having a disaster and writing a story about it! Give these guys credit for letting you see what happens when it ALL goes bad. Disaster recovery is hard to sell and hard to do, reading the article might give you an idea that will save you some time and/or data one day.
</p>]]></description><guid>http://www.sqlservercentral.com/articles/Administration/disasterintherealworld2/747/</guid><pubDate>Fri, 14 Dec 2012 07:00:00 UT</pubDate><link>http://www.sqlservercentral.com/articles/Administration/disasterintherealworld2/747/</link></item><item><title>Data Distribution with SQL Server Replication</title><description><![CDATA[<p>This paper provides a foundation for understanding data replication as well as a discussion of the criteria for selecting an appropriate replication technology. </p>]]></description><guid>http://www.sqlservercentral.com/articles/Replication/95012/</guid><pubDate>Mon, 10 Dec 2012 07:00:00 UT</pubDate><link>http://www.sqlservercentral.com/articles/Replication/95012/</link></item><item><title>Designing &amp; Maintaining SQL Server Transactional Replication Environments</title><description><![CDATA[<p>Microsoft IT protects against unplanned Transactional Replication outages and issues by using best practices and proactive monitoring. This results in increased stability, simplified management and improved performance of transactional replication environments.</p>]]></description><guid>http://www.sqlservercentral.com/redirect/articles/93032/</guid><pubDate>Fri, 12 Oct 2012 06:00:00 UT</pubDate><link>http://www.sqlservercentral.com/redirect/articles/93032/</link></item><item><title>Process to truncate transaction log of replicated database</title><description><![CDATA[<p>This article demonstrated the steps which you must follow to gracefully truncate the publisher database transaction log file by resetting replication. </p><!-- disturbing m2 (DBA Bundle) -->
<table border="0" cellpadding="0" cellspacing="10" style="width: 100%;"> <colgroup>  <col width="68" />  <col width="1266" /> </colgroup> <tbody>  <tr align="left" valign="top">   <td>    <a href="http://www.red-gate.com/products/dba/dba-bundle/entrypage/hard-earned-lessons-4?utm_source=ssc&utm_medium=pubad&utm_content=disturbing_m2&utm_campaign=sqldbabundle&utm_term=rss-20233"><img src="http://assets.red-gate.com/external/SSC/top5_68x68.gif" alt="sqldbabundle"></td>   <td><strong>Top 5 hard-earned Lessons of a DBA </strong><br />New! Part 4, ‘Disturbing Development’ by Grant Fritchey, features the return of Joe Deebeeay and a server-threatening encounter with ORMs -  <a href="http://www.red-gate.com/products/dba/dba-bundle/entrypage/hard-earned-lessons-4?utm_source=ssc&utm_medium=pubad&utm_content=disturbing_m2&utm_campaign=sqldbabundle&utm_term=rss-20233">read it here</a></td>  </tr> </tbody></table>
]]></description><guid>http://www.sqlservercentral.com/articles/Replication/91016/</guid><pubDate>Tue, 24 Jul 2012 06:00:00 UT</pubDate><link>http://www.sqlservercentral.com/articles/Replication/91016/</link></item><item><title>Steps to clean up orphaned replication settings in SQL Server </title><description><![CDATA[<p>Learn how to clean up your orphaned replication settings.</p>]]></description><guid>http://www.sqlservercentral.com/redirect/articles/91630/</guid><pubDate>Thu, 05 Jul 2012 06:00:00 UT</pubDate><link>http://www.sqlservercentral.com/redirect/articles/91630/</link></item><item><title>Transaction Replication Publisher failover to Mirror</title><description><![CDATA[<p>Transaction Replication Publisher failover/failback to mirror standby with automatic redirection of the subscriber and client application.</p>]]></description><guid>http://www.sqlservercentral.com/articles/SQL+Server+2008/88505/</guid><pubDate>Thu, 28 Jun 2012 06:00:00 UT</pubDate><link>http://www.sqlservercentral.com/articles/SQL+Server+2008/88505/</link></item><item><title>The Trouble with Transactional Replication and large articles.</title><description><![CDATA[<p>This article will show you one way to quickly restore SQL Server replication with huge tables.</p>]]></description><guid>http://www.sqlservercentral.com/articles/Replication/88155/</guid><pubDate>Fri, 18 May 2012 06:00:00 UT</pubDate><link>http://www.sqlservercentral.com/articles/Replication/88155/</link></item><item><title>Transaction Replication Latency Diagnosis</title><description><![CDATA[<p>Identify resource bottlenecks in a stressed transaction replication topology using PERFMON/PAL and system wait stats</p>]]></description><guid>http://www.sqlservercentral.com/articles/PerfMon/88251/</guid><pubDate>Wed, 09 May 2012 06:00:00 UT</pubDate><link>http://www.sqlservercentral.com/articles/PerfMon/88251/</link></item><item><title>Stairway to SQL Server Replication - Level 10: Troubleshooting</title><description><![CDATA[<p>The final level of this Stairway takes you through how to identify and fix common errors.</p>]]></description><guid>http://www.sqlservercentral.com/articles/Stairway+Series/72452/</guid><pubDate>Wed, 18 Apr 2012 06:00:00 UT</pubDate><link>http://www.sqlservercentral.com/articles/Stairway+Series/72452/</link></item><item><title>Understanding Retention Periods for SQL Server Transactional Replication</title><description><![CDATA[<p>I have transactional replication configured in production. I have heard about the replication retention period, but what is the significance of this. Would there be any impact to my replication configuration if data is not synchronized with the subscriptions within the retention period?</p>]]></description><guid>http://www.sqlservercentral.com/redirect/articles/89992/</guid><pubDate>Tue, 17 Apr 2012 06:00:00 UT</pubDate><link>http://www.sqlservercentral.com/redirect/articles/89992/</link></item><item><title>Renaming a Published SQL Server Database</title><description><![CDATA[<p>I have transactional replication configured in production. I am wondering if we could rename the publication database in transactional replication without having to drop and recreate the replication set up. Also, is it possible to rename the database files of the publication database without affecting the replication configuration.</p>]]></description><guid>http://www.sqlservercentral.com/redirect/articles/89342/</guid><pubDate>Tue, 10 Apr 2012 06:00:00 UT</pubDate><link>http://www.sqlservercentral.com/redirect/articles/89342/</link></item><item><title>Init Replication From Backup</title><description><![CDATA[<p>One of the great features with SQL Replication is the ability to initialize a subscription from backup instead of from a snapshot.  The official use for this is to take a database backup and restore it to a subscriber then replicate any additional changes to the backup.</p>]]></description><guid>http://www.sqlservercentral.com/redirect/articles/89344/</guid><pubDate>Mon, 02 Apr 2012 06:00:00 UT</pubDate><link>http://www.sqlservercentral.com/redirect/articles/89344/</link></item><item><title>Stairway to SQL Server Replication - Level 9: The Replication Monitor</title><description><![CDATA[<p>Introducing the replication monitor and how to use it to monitor replication health. It also introduces tracer tokens.</p>]]></description><guid>http://www.sqlservercentral.com/articles/Stairway+Series/72451/</guid><pubDate>Wed, 21 Mar 2012 06:00:00 UT</pubDate><link>http://www.sqlservercentral.com/articles/Stairway+Series/72451/</link></item><item><title>Stairway to SQL Server Replication - Level 8: Merge Replication – How it works</title><description><![CDATA[<p>How merge replication works, including the impact on the published database. The merge agent, different conflict situations and their resolutions are introduced.</p>]]></description><guid>http://www.sqlservercentral.com/articles/Stairway+Series/72450/</guid><pubDate>Fri, 02 Mar 2012 07:00:00 UT</pubDate><link>http://www.sqlservercentral.com/articles/Stairway+Series/72450/</link></item><item><title>Stairway to SQL Server Replication - Level 7: Merge Replication – Subscription</title><description><![CDATA[<p>This level of the Stairway will cover the details of SQL Server transactional and merge replication, from understanding the basic terminology and methodology of setting up replication, to describing how it works and how the basic replication processes can be monitored. </p>]]></description><guid>http://www.sqlservercentral.com/articles/Stairway+Series/72449/</guid><pubDate>Fri, 03 Feb 2012 07:00:00 UT</pubDate><link>http://www.sqlservercentral.com/articles/Stairway+Series/72449/</link></item><item><title>Stairway to SQL Server Replication - Level 6: Merge Replication - Publication</title><description><![CDATA[<p>This level covers the details of SQL Server transactional and merge replication, from understanding the basic terminology and methodology of setting up replication, to describing how it works and how the basic replication processes can be monitored. </p>]]></description><guid>http://www.sqlservercentral.com/articles/Stairway+Series/72448/</guid><pubDate>Fri, 13 Jan 2012 07:00:00 UT</pubDate><link>http://www.sqlservercentral.com/articles/Stairway+Series/72448/</link></item><item><title>Options to reinitialize subscriptions in SQL Server replication</title><description><![CDATA[<p>I have transactional replication configured in my production environment with multiple subscribers.  The business team has requested that one of the subscriptions be reinitialized, because they think there is some missing data. In this tip we look at the different options that you can use to reinitialize a subscription for transactional replication.</p>]]></description><guid>http://www.sqlservercentral.com/redirect/articles/86993/</guid><pubDate>Tue, 27 Dec 2011 07:00:00 UT</pubDate><link>http://www.sqlservercentral.com/redirect/articles/86993/</link></item><item><title>Options to not replicate SQL Server DELETE commands</title><description><![CDATA[<p>I have transactional replication configured in my production environment. The business team has requested that I do not replicate delete operations on certain articles.  In this tip we look at a couple of options to not replicate DELETE commands.</p>]]></description><guid>http://www.sqlservercentral.com/redirect/articles/76827/</guid><pubDate>Fri, 04 Nov 2011 06:00:00 UT</pubDate><link>http://www.sqlservercentral.com/redirect/articles/76827/</link></item><item><title>An Easy Way to Monitor SQL Server Replication  </title><description><![CDATA[<p>In SQL Server, replication is a widely adopted technology for the purpose of real-time data replication between SQL servers. It serves the purpose of keeping data consistent between multiple end points. So the last thing we want to hear from clients is that data is no longer in synch, and as DBA, we don't want to be the last person to realize replication is out of order or broken. Here are some steps you can take to monitor SQL Server replication.</p>]]></description><guid>http://www.sqlservercentral.com/redirect/articles/76502/</guid><pubDate>Wed, 26 Oct 2011 06:00:00 UT</pubDate><link>http://www.sqlservercentral.com/redirect/articles/76502/</link></item><item><title>Update multiple servers in a single bound</title><description><![CDATA[<p>Learn how you can update multiple servers in a single bound with this technique from Kimberly Killian.</p>]]></description><guid>http://www.sqlservercentral.com/articles/Replication/75221/</guid><pubDate>Mon, 24 Oct 2011 06:00:00 UT</pubDate><link>http://www.sqlservercentral.com/articles/Replication/75221/</link></item><item><title>Centrally collect replication conflicts and send an alert</title><description><![CDATA[<p>Automatically capture replication conflicts and generate an automated email notification.</p><!-- version control now (SQL Source Control) -->
<table border="0" cellpadding="0" cellspacing="10" style="width: 100%;"> <colgroup>  <col width="68" />  <col width="1266" /> </colgroup> <tbody>  <tr align="left" valign="top">   <td>    <a href="http://www.red-gate.com/products/sql-development/sql-source-control/entrypage/version-control-now?utm_source=ssc&utm_medium=pubad&utm_content=version_control_now&utm_campaign=sqlsourcecontrol&utm_term=rss-20229"><img src="http://assets.red-gate.com/external/SSC/srccon68x68.gif" alt="sqlsourcecontrol"></td>   <td><strong>Get your SQL Server database under version control now!</strong><br />Version control is standard for applications, but databases haven’t caught up. So how can you bring database development up to speed? Why should you start?  <a href="http://www.red-gate.com/products/sql-development/sql-source-control/entrypage/version-control-now?utm_source=ssc&utm_medium=pubad&utm_content=version_control_now&utm_campaign=sqlsourcecontrol&utm_term=rss-20229">Find out…</a></td>  </tr> </tbody></table>
]]></description><guid>http://www.sqlservercentral.com/articles/Replication/75190/</guid><pubDate>Mon, 17 Oct 2011 06:00:00 UT</pubDate><link>http://www.sqlservercentral.com/articles/Replication/75190/</link></item><item><title>When Did Merge Replication Subscribers Last Sync?</title><description><![CDATA[<p>The article presents an automated process to see when remote servers last synced to publisher and send notification reminders.</p>]]></description><guid>http://www.sqlservercentral.com/articles/Merge+Replication/74294/</guid><pubDate>Thu, 18 Aug 2011 06:00:00 UT</pubDate><link>http://www.sqlservercentral.com/articles/Merge+Replication/74294/</link></item><item><title>Stairway to SQL Server Replication - Level 5: Transactional Replication &amp; How it works</title><description><![CDATA[<p>This level covers the details of SQL Server transactional and merge replication, from understanding the basic terminology and methodology of setting up replication, to describing how it works and how the basic replication processes can be monitored. </p>]]></description><guid>http://www.sqlservercentral.com/articles/Stairway+Series/Transactional+Replication+%e2%80%93+How+it+works/72277/</guid><pubDate>Wed, 20 Jul 2011 06:00:00 UT</pubDate><link>http://www.sqlservercentral.com/articles/Stairway+Series/Transactional+Replication+%e2%80%93+How+it+works/72277/</link></item><item><title>Monitor SQL Server Replication Jobs</title><description><![CDATA[<p>The Replication infrastructure in SQL Server is implemented using SQL Server Agent to execute the various components involved in the form of a job (e.g. LogReader agent job, Distribution agent job, Merge agent job) SQL Server jobs execute a binary executable file which is basically C++ code.</p>]]></description><guid>http://www.sqlservercentral.com/redirect/articles/74520/</guid><pubDate>Mon, 11 Jul 2011 06:00:00 UT</pubDate><link>http://www.sqlservercentral.com/redirect/articles/74520/</link></item><item><title>SQL Server Replication: Providing High Availability using Database Mirroring</title><description><![CDATA[<p>This white paper describes how to use database mirroring to increase the availability of the replication stream in a transactional environment. The document covers setting up replication in a mirrored environment, the effect of mirroring partnership state changes, and the effect of mirroring failovers on replication. In addition, it describes how to use LSN-based initialization to recover from the failover of a mirrored Subscriber database.</p>]]></description><guid>http://www.sqlservercentral.com/redirect/articles/73563/</guid><pubDate>Tue, 17 May 2011 06:00:00 UT</pubDate><link>http://www.sqlservercentral.com/redirect/articles/73563/</link></item></channel></rss>