<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>
<channel>
	<title>SQL Server Performance &#187; Replication</title>
	<atom:link href="http://www.sql-server-performance.com/tag/replication/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.sql-server-performance.com</link>
	<description>SQL Server Performance Tuning</description>
	<lastBuildDate>Wed, 15 May 2013 08:10:41 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
		<item>
		<title>Transactional Replication – Unable to Replicate Data onto the Subscriber  &#8211;  A Practical Example</title>
		<link>http://www.sql-server-performance.com/2013/transactional-replication-unable-to-replicate-data-onto-the-subscriber/</link>
		<comments>http://www.sql-server-performance.com/2013/transactional-replication-unable-to-replicate-data-onto-the-subscriber/#comments</comments>
		<pubDate>Mon, 04 Mar 2013 10:55:17 +0000</pubDate>
		<dc:creator>satnam singh</dc:creator>
				<category><![CDATA[General DBA]]></category>
		<category><![CDATA[Reporting]]></category>
		<category><![CDATA[Replication]]></category>
		<category><![CDATA[SSRS]]></category>
		<guid isPermaLink="false">http://www.sql-server-performance.com/?p=2906</guid>
		<description><![CDATA[Scenario: A couple of days back, I got a call from one of my users saying that the Data is not being replicated properly onto the Production Reporting Server from the Production OLTP server. We have Transactional Replication scheduled for every 15 minutes between our OLTP and the Reporting server. Approach: I started investigating this [...]]]></description>
		<wfw:commentRss>http://www.sql-server-performance.com/2013/transactional-replication-unable-to-replicate-data-onto-the-subscriber/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>Replication Without Creating a Snapshot</title>
		<link>http://www.sql-server-performance.com/2012/replication-without-creating-snapshot/</link>
		<comments>http://www.sql-server-performance.com/2012/replication-without-creating-snapshot/#comments</comments>
		<pubDate>Tue, 28 Feb 2012 09:09:19 +0000</pubDate>
		<dc:creator>Dinesh Asanka</dc:creator>
				<category><![CDATA[General DBA]]></category>
		<category><![CDATA[Replication]]></category>
		<guid isPermaLink="false">http://www.sql-server-performance.com/?p=2913</guid>
		<description><![CDATA[In replication, the standard way of creating a publisher is to create a publication with a snapshot (which is what all the documentation recommends). However there are a few problems with this method: Creating the snapshots and then applying them is time consuming. Snapshots will consume disk space. There is an alternative to this, where [...]]]></description>
		<wfw:commentRss>http://www.sql-server-performance.com/2012/replication-without-creating-snapshot/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>SQL Server Agent Alter Column Error</title>
		<link>http://www.sql-server-performance.com/2011/sql-server-agent-alter-column-error/</link>
		<comments>http://www.sql-server-performance.com/2011/sql-server-agent-alter-column-error/#comments</comments>
		<pubDate>Mon, 26 Sep 2011 10:25:21 +0000</pubDate>
		<dc:creator>Dinesh Asanka</dc:creator>
				<category><![CDATA[Errors]]></category>
		<category><![CDATA[Agent]]></category>
		<category><![CDATA[Replication]]></category>
		<guid isPermaLink="false">http://www.sql-server-performance.com/?p=2690</guid>
		<description><![CDATA[Replication Agent will fail when attempting to alter a column in the publisher which is part of an index. For example, let’s say you have table like following: CREATE TABLE [dbo].[Employees]( [ID] [int] IDENTITY(1,1) NOT NULL, [FirstName] [nvarchar](50) NULL, [LastName] [varchar](50) NULL, CONSTRAINT [PK_Employees] PRIMARY KEY CLUSTERED ( [ID] ASC ) ) ON [PRIMARY] And [...]]]></description>
		<wfw:commentRss>http://www.sql-server-performance.com/2011/sql-server-agent-alter-column-error/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Manage and Monitor Identity Ranges in SQL Server Transactional Replication</title>
		<link>http://www.sql-server-performance.com/2011/identity-ranges-transactional-replication/</link>
		<comments>http://www.sql-server-performance.com/2011/identity-ranges-transactional-replication/#comments</comments>
		<pubDate>Mon, 21 Feb 2011 01:12:50 +0000</pubDate>
		<dc:creator>Yaniv Etrogi</dc:creator>
				<category><![CDATA[General DBA]]></category>
		<category><![CDATA[Identity Ranges]]></category>
		<category><![CDATA[INSERT]]></category>
		<category><![CDATA[int]]></category>
		<category><![CDATA[Monitoring]]></category>
		<category><![CDATA[range]]></category>
		<category><![CDATA[Replication]]></category>
		<category><![CDATA[Transactional Replication]]></category>
		<guid isPermaLink="false">http://www.sql-server-performance.com/?=1948</guid>
		<description><![CDATA[Problem When using transactional replication to replicate data in a one way topology from a publisher to a read-only subscriber(s) there is no need to manage identity ranges. However, when using&#160; transactional replication to replicate data in a two way replication topology - between two or more servers there is a need to manage identity [...]]]></description>
		<wfw:commentRss>http://www.sql-server-performance.com/2011/identity-ranges-transactional-replication/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Monitoring Transactional Replication – The Distribution Queue</title>
		<link>http://www.sql-server-performance.com/2011/transactional-replication-distribution-queue/</link>
		<comments>http://www.sql-server-performance.com/2011/transactional-replication-distribution-queue/#comments</comments>
		<pubDate>Mon, 07 Feb 2011 01:12:50 +0000</pubDate>
		<dc:creator>Yaniv Etrogi</dc:creator>
				<category><![CDATA[General DBA]]></category>
		<category><![CDATA[Replication]]></category>
		<guid isPermaLink="false">http://www.sql-server-performance.com/?=1938</guid>
		<description><![CDATA[Note : The scripts for this article can be downloaded here. Monitoring the distribution queue is an important link in the chain of transactions delivery over a replicated topology. A chain that includes the log reader agent scanning the published database&#8217;s transaction log for commands to be moved to the distribution database from which a [...]]]></description>
		<wfw:commentRss>http://www.sql-server-performance.com/2011/transactional-replication-distribution-queue/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Setting up Transactional Replication in SQL Server 2008 R2.</title>
		<link>http://www.sql-server-performance.com/2010/transactional-replication-2008-r2/</link>
		<comments>http://www.sql-server-performance.com/2010/transactional-replication-2008-r2/#comments</comments>
		<pubDate>Mon, 08 Nov 2010 01:12:50 +0000</pubDate>
		<dc:creator>satnam singh</dc:creator>
				<category><![CDATA[Performance Tuning]]></category>
		<category><![CDATA[2008 R2]]></category>
		<category><![CDATA[publisher]]></category>
		<category><![CDATA[Replication]]></category>
		<category><![CDATA[schema changes]]></category>
		<category><![CDATA[Snapshot]]></category>
		<category><![CDATA[subscriber database]]></category>
		<category><![CDATA[Transactional Replication]]></category>
		<guid isPermaLink="false">http://www.sql-server-performance.com/?=1907</guid>
		<description><![CDATA[Setting up Transactional Replication in SQL Server 2008 R2. Replication is one of the High Availability features available in SQL Server. Transactional Replication is used when DML or DDL schema changes performed on an object of a database on one server needs to be reflected on the database residing on another server. This change happens [...]]]></description>
		<wfw:commentRss>http://www.sql-server-performance.com/2010/transactional-replication-2008-r2/feed/</wfw:commentRss>
		<slash:comments>48</slash:comments>
		</item>
	</channel>
</rss>
