<?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: Database Log Shipping Interview Questions and Answers (Day-3)	</title>
	<atom:link href="https://www.dbrnd.com/2016/07/sql-server-database-log-shipping-interview-questions-and-answers-restoring-standby-mode-tuf-file-sp_resolve_logins-day-3/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.dbrnd.com/2016/07/sql-server-database-log-shipping-interview-questions-and-answers-restoring-standby-mode-tuf-file-sp_resolve_logins-day-3/</link>
	<description>BIGData &#124; NoSQL &#124; MSSQL &#124; MySQL &#124; PostgreSQL</description>
	<lastBuildDate>Fri, 20 Jan 2017 17:48:24 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=7.0.4</generator>
	<item>
		<title>
		By: Anvesh Patel		</title>
		<link>https://www.dbrnd.com/2016/07/sql-server-database-log-shipping-interview-questions-and-answers-restoring-standby-mode-tuf-file-sp_resolve_logins-day-3/#comment-5471</link>

		<dc:creator><![CDATA[Anvesh Patel]]></dc:creator>
		<pubDate>Fri, 20 Jan 2017 17:48:24 +0000</pubDate>
		<guid isPermaLink="false">https://www.dbrnd.com/?p=3251#comment-5471</guid>

					<description><![CDATA[In reply to &lt;a href=&quot;https://www.dbrnd.com/2016/07/sql-server-database-log-shipping-interview-questions-and-answers-restoring-standby-mode-tuf-file-sp_resolve_logins-day-3/#comment-5470&quot;&gt;anil&lt;/a&gt;.

You can perform shrink on the primary database it will be carried over to the secondary database, it will not break your log shipping.But only if your secondary is in a read-only state.If you have configured your secondary in a no-recovery mode the changes will not be carried over to secondary as no operation can be performed in no-recovery mode. But remember shrinking Data file is not a best practice.]]></description>
			<content:encoded><![CDATA[<p>In reply to <a href="https://www.dbrnd.com/2016/07/sql-server-database-log-shipping-interview-questions-and-answers-restoring-standby-mode-tuf-file-sp_resolve_logins-day-3/#comment-5470">anil</a>.</p>
<p>You can perform shrink on the primary database it will be carried over to the secondary database, it will not break your log shipping.But only if your secondary is in a read-only state.If you have configured your secondary in a no-recovery mode the changes will not be carried over to secondary as no operation can be performed in no-recovery mode. But remember shrinking Data file is not a best practice.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: anil		</title>
		<link>https://www.dbrnd.com/2016/07/sql-server-database-log-shipping-interview-questions-and-answers-restoring-standby-mode-tuf-file-sp_resolve_logins-day-3/#comment-5470</link>

		<dc:creator><![CDATA[anil]]></dc:creator>
		<pubDate>Fri, 20 Jan 2017 14:42:27 +0000</pubDate>
		<guid isPermaLink="false">https://www.dbrnd.com/?p=3251#comment-5470</guid>

					<description><![CDATA[what will happen in secondary server when we perform shrink operation in primary server database in sql log shipping]]></description>
			<content:encoded><![CDATA[<p>what will happen in secondary server when we perform shrink operation in primary server database in sql log shipping</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
