<?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; Yaniv Etrogi</title>
	<atom:link href="http://www.sql-server-performance.com/author/yanivetrogi/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.sql-server-performance.com</link>
	<description>SQL Server Performance Tuning</description>
	<lastBuildDate>Wed, 22 May 2013 06:37:33 +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>Monitor SQL Server Replication Jobs</title>
		<link>http://www.sql-server-performance.com/2011/monitor-sql-server-replication-jobs/</link>
		<comments>http://www.sql-server-performance.com/2011/monitor-sql-server-replication-jobs/#comments</comments>
		<pubDate>Wed, 01 Jun 2011 03:39:54 +0000</pubDate>
		<dc:creator>Yaniv Etrogi</dc:creator>
				<category><![CDATA[Articles]]></category>
		<category><![CDATA[FAQ]]></category>
		<category><![CDATA[General DBA]]></category>
		<category><![CDATA[Agent]]></category>
		<category><![CDATA[Jobs]]></category>
		<category><![CDATA[Replication Jobs. Job]]></category>
		<guid isPermaLink="false">http://www.sql-server-performance.com/?p=2545</guid>
		<description><![CDATA[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. You can download all the scripts for this [...]]]></description>
		<wfw:commentRss>http://www.sql-server-performance.com/2011/monitor-sql-server-replication-jobs/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>Monitoring Table Size Growth in SQL Server</title>
		<link>http://www.sql-server-performance.com/2010/monitor-data-growth/</link>
		<comments>http://www.sql-server-performance.com/2010/monitor-data-growth/#comments</comments>
		<pubDate>Wed, 01 Dec 2010 01:12:50 +0000</pubDate>
		<dc:creator>Yaniv Etrogi</dc:creator>
				<category><![CDATA[General DBA]]></category>
		<category><![CDATA[Agent]]></category>
		<category><![CDATA[Delta]]></category>
		<category><![CDATA[exec statement]]></category>
		<category><![CDATA[Table Size Growth]]></category>
		<guid isPermaLink="false">http://www.sql-server-performance.com/?=1912</guid>
		<description><![CDATA[General In this article I introduce a simple process that saves tables size information at points in time which latter allows for tracking down table growth over time. The process is useful in monitoring data growth over time and lets you see what tables are growing rapidly in what databases and can also help in [...]]]></description>
		<wfw:commentRss>http://www.sql-server-performance.com/2010/monitor-data-growth/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Troubleshoot Database Concurrency in SQL Server with sp_locks</title>
		<link>http://www.sql-server-performance.com/2010/concurrency-sp-locks/</link>
		<comments>http://www.sql-server-performance.com/2010/concurrency-sp-locks/#comments</comments>
		<pubDate>Tue, 19 Oct 2010 01:12:50 +0000</pubDate>
		<dc:creator>Yaniv Etrogi</dc:creator>
				<category><![CDATA[General DBA]]></category>
		<category><![CDATA[Performance Tuning]]></category>
		<category><![CDATA[Concurrency]]></category>
		<category><![CDATA[sp_locks]]></category>
		<guid isPermaLink="false">http://www.sql-server-performance.com/?=1903</guid>
		<description><![CDATA[General Database concurrency can be defined as the number of users that can work at a given database at the same time while not effecting or interfering with eachother&#8217;s work. The greater the number of users working at the same time the higher concurrency is. SQL Server holds Locks on user data to protect data [...]]]></description>
		<wfw:commentRss>http://www.sql-server-performance.com/2010/concurrency-sp-locks/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Create a Performance Baseline Repository</title>
		<link>http://www.sql-server-performance.com/2010/baseline-repository/</link>
		<comments>http://www.sql-server-performance.com/2010/baseline-repository/#comments</comments>
		<pubDate>Wed, 08 Sep 2010 01:12:50 +0000</pubDate>
		<dc:creator>Yaniv Etrogi</dc:creator>
				<category><![CDATA[General DBA]]></category>
		<category><![CDATA[Performance Baseline Repository]]></category>
		<guid isPermaLink="false">http://www.sql-server-performance.com/?=1897</guid>
		<description><![CDATA[Terms used in this article Execution or SQL Execution represents a call to a Stored Procedure or an SQL Batch. General Description This process creates a Baseline repository that holds summarized data of all SQL Executions executed on an instance of SQL Server. The repository lights up your SQL Server&#8217;s activity and exposes interesting information [...]]]></description>
		<wfw:commentRss>http://www.sql-server-performance.com/2010/baseline-repository/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
	</channel>
</rss>
