<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: SQL Server Log Shipping For Large Databases</title>
	<atom:link href="http://www.sql-server-performance.com/2011/sql-server-log-shipping-for-large-databases/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.sql-server-performance.com/2011/sql-server-log-shipping-for-large-databases/</link>
	<description>SQL Server Performance Tuning</description>
	<lastBuildDate>Fri, 17 May 2013 13:31:24 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
	<item>
		<title>By: Shankar Reddy</title>
		<link>http://www.sql-server-performance.com/2011/sql-server-log-shipping-for-large-databases/#comment-1236</link>
		<dc:creator>Shankar Reddy</dc:creator>
		<pubDate>Wed, 18 Jan 2012 06:59:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.sql-server-performance.com/?p=2590#comment-1236</guid>
		<description><![CDATA[Nice .you given step by step process could you please provide log shipping errors and solutions .information]]></description>
		<content:encoded><![CDATA[<p>Nice .you given step by step process could you please provide log shipping errors and solutions .information</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Shankar Reddy</title>
		<link>http://www.sql-server-performance.com/2011/sql-server-log-shipping-for-large-databases/#comment-1235</link>
		<dc:creator>Shankar Reddy</dc:creator>
		<pubDate>Wed, 18 Jan 2012 06:58:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.sql-server-performance.com/?p=2590#comment-1235</guid>
		<description><![CDATA[Gud article you given step by step process could you please provide log shipping errors and solutions .information]]></description>
		<content:encoded><![CDATA[<p>Gud article you given step by step process could you please provide log shipping errors and solutions .information</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: DBA</title>
		<link>http://www.sql-server-performance.com/2011/sql-server-log-shipping-for-large-databases/#comment-632</link>
		<dc:creator>DBA</dc:creator>
		<pubDate>Tue, 27 Sep 2011 10:54:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.sql-server-performance.com/?p=2590#comment-632</guid>
		<description><![CDATA[This goes back to the point I made. I can&#039;t quite see how I would treat Log Shipping for a &#039;small&#039; database any differently.
Nice article but seems to have missed the point.]]></description>
		<content:encoded><![CDATA[<p>This goes back to the point I made. I can&#8217;t quite see how I would treat Log Shipping for a &#8216;small&#8217; database any differently.<br />
Nice article but seems to have missed the point.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jan S./SEAQL</title>
		<link>http://www.sql-server-performance.com/2011/sql-server-log-shipping-for-large-databases/#comment-631</link>
		<dc:creator>Jan S./SEAQL</dc:creator>
		<pubDate>Fri, 23 Sep 2011 16:34:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.sql-server-performance.com/?p=2590#comment-631</guid>
		<description><![CDATA[Hi,
Thanks for providing a comprehensive guide.  I would like to mention that in SQL Server 2008 R2 Standard and Enterprise, you can use compressed backups as the native SQL Server backup option, thus eliminating the extra RAR step.  Log Shipping under these versions can also utilize backup compression, so your time to backup and restore and time to transfer the backup is shorter.  It is well worth investigating and is a great time, disk space, and bandwidth saver.  Thanks again.
Jan S./SEAQL]]></description>
		<content:encoded><![CDATA[<p>Hi,<br />
Thanks for providing a comprehensive guide.  I would like to mention that in SQL Server 2008 R2 Standard and Enterprise, you can use compressed backups as the native SQL Server backup option, thus eliminating the extra RAR step.  Log Shipping under these versions can also utilize backup compression, so your time to backup and restore and time to transfer the backup is shorter.  It is well worth investigating and is a great time, disk space, and bandwidth saver.  Thanks again.</p>
<p>Jan S./SEAQL</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bvach</title>
		<link>http://www.sql-server-performance.com/2011/sql-server-log-shipping-for-large-databases/#comment-630</link>
		<dc:creator>Bvach</dc:creator>
		<pubDate>Fri, 23 Sep 2011 11:51:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.sql-server-performance.com/?p=2590#comment-630</guid>
		<description><![CDATA[You might also want to ensure that Backup compression is being used, since the first backup and logs will be shipped across the network]]></description>
		<content:encoded><![CDATA[<p>You might also want to ensure that Backup compression is being used, since the first backup and logs will be shipped across the network</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: DBA</title>
		<link>http://www.sql-server-performance.com/2011/sql-server-log-shipping-for-large-databases/#comment-629</link>
		<dc:creator>DBA</dc:creator>
		<pubDate>Fri, 23 Sep 2011 11:06:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.sql-server-performance.com/?p=2590#comment-629</guid>
		<description><![CDATA[In the start of your article you mention that using the GUI is not a good option. Yet throughout the procedure you use the GUI.
Can you clarify this a bit further, where did you NOT use the GUI?]]></description>
		<content:encoded><![CDATA[<p>In the start of your article you mention that using the GUI is not a good option. Yet throughout the procedure you use the GUI.<br />
Can you clarify this a bit further, where did you NOT use the GUI?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: vinay</title>
		<link>http://www.sql-server-performance.com/2011/sql-server-log-shipping-for-large-databases/#comment-606</link>
		<dc:creator>vinay</dc:creator>
		<pubDate>Wed, 14 Sep 2011 07:13:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.sql-server-performance.com/?p=2590#comment-606</guid>
		<description><![CDATA[hi,
Its a very nice article. But why while adding secondary server screenshots are not given for &#039;Initialize Secondary Database&#039; and adding secondary server by using &#039;Add&#039; in detail.]]></description>
		<content:encoded><![CDATA[<p>hi,</p>
<p>Its a very nice article. But why while adding secondary server screenshots are not given for &#8216;Initialize Secondary Database&#8217; and adding secondary server by using &#8216;Add&#8217; in detail.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Psalm</title>
		<link>http://www.sql-server-performance.com/2011/sql-server-log-shipping-for-large-databases/#comment-558</link>
		<dc:creator>Psalm</dc:creator>
		<pubDate>Thu, 25 Aug 2011 09:13:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.sql-server-performance.com/?p=2590#comment-558</guid>
		<description><![CDATA[Very good article. Can you please elaborate on how to monitor log shipping, especially the way the synchronization works. How can one knows its synchronize/ up to date with the primary server
Thank you.]]></description>
		<content:encoded><![CDATA[<p>Very good article. Can you please elaborate on how to monitor log shipping, especially the way the synchronization works. How can one knows its synchronize/ up to date with the primary server</p>
<p>Thank you.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Name (required)</title>
		<link>http://www.sql-server-performance.com/2011/sql-server-log-shipping-for-large-databases/#comment-516</link>
		<dc:creator>Name (required)</dc:creator>
		<pubDate>Thu, 11 Aug 2011 14:04:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.sql-server-performance.com/?p=2590#comment-516</guid>
		<description><![CDATA[Nice article]]></description>
		<content:encoded><![CDATA[<p>Nice article</p>
]]></content:encoded>
	</item>
</channel>
</rss>
