<?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; Log Shipping</title>
	<atom:link href="http://www.sql-server-performance.com/tag/log-shipping/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.sql-server-performance.com</link>
	<description>SQL Server Performance Tuning</description>
	<lastBuildDate>Tue, 18 Jun 2013 05:40:59 +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>Automating  SQL Server Transactional Log Shipping Alerts</title>
		<link>http://www.sql-server-performance.com/2012/automating-sql-server-transactional-log-shipping-alerts/</link>
		<comments>http://www.sql-server-performance.com/2012/automating-sql-server-transactional-log-shipping-alerts/#comments</comments>
		<pubDate>Tue, 02 Oct 2012 03:40:02 +0000</pubDate>
		<dc:creator>satnam singh</dc:creator>
				<category><![CDATA[General DBA]]></category>
		<category><![CDATA[Alert]]></category>
		<category><![CDATA[Emai]]></category>
		<category><![CDATA[Log Shipping]]></category>
		<guid isPermaLink="false">http://www.sql-server-performance.com/?p=3251</guid>
		<description><![CDATA[DBAs often follow a practice of using the Transactional Log Shipping Monitor in SSMS to ensure that the Log Shipping is running without any issues. However, it is not always possible to do 24/7 monitoring using the Log Shipping monitor. The alert messages generated by third party monitoring systems can be overkill and generate messages [...]]]></description>
		<wfw:commentRss>http://www.sql-server-performance.com/2012/automating-sql-server-transactional-log-shipping-alerts/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>SQL Server Log Shipping For Large Databases</title>
		<link>http://www.sql-server-performance.com/2011/sql-server-log-shipping-for-large-databases/</link>
		<comments>http://www.sql-server-performance.com/2011/sql-server-log-shipping-for-large-databases/#comments</comments>
		<pubDate>Mon, 25 Jul 2011 00:17:31 +0000</pubDate>
		<dc:creator>satnam singh</dc:creator>
				<category><![CDATA[General DBA]]></category>
		<category><![CDATA[Backup]]></category>
		<category><![CDATA[Disaster Recovery]]></category>
		<category><![CDATA[Log Shipping]]></category>
		<guid isPermaLink="false">http://www.sql-server-performance.com/?p=2590</guid>
		<description><![CDATA[Scenario:  A couple of days back I was setting up a DR plan for one of our most mission critical DB servers which was hosting around 10 databases having size of 10, 23, 5, 7.4, 1.8, 6.2, 7.9, 5.53, 8.7 and 125 GB respectively. I decided to implement Log Shipping as a part of the [...]]]></description>
		<wfw:commentRss>http://www.sql-server-performance.com/2011/sql-server-log-shipping-for-large-databases/feed/</wfw:commentRss>
		<slash:comments>9</slash:comments>
		</item>
	</channel>
</rss>
