<?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: How To: Configure Read-Only Routing for Availability Groups	</title>
	<atom:link href="https://sqlsolutionsgroup.com/how-to-configure-read-only-routing-for-availability-groups/feed/" rel="self" type="application/rss+xml" />
	<link>https://sqlsolutionsgroup.com/how-to-configure-read-only-routing-for-availability-groups/</link>
	<description></description>
	<lastBuildDate>Mon, 22 Jul 2024 20:46:41 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.9.4</generator>
	<item>
		<title>
		By: Randy Knight		</title>
		<link>https://sqlsolutionsgroup.com/how-to-configure-read-only-routing-for-availability-groups/#comment-33582</link>

		<dc:creator><![CDATA[Randy Knight]]></dc:creator>
		<pubDate>Mon, 22 Jul 2024 20:46:41 +0000</pubDate>
		<guid isPermaLink="false">https://sqlsolutionsgroup.com/?p=6282#comment-33582</guid>

					<description><![CDATA[In reply to &lt;a href=&quot;https://sqlsolutionsgroup.com/how-to-configure-read-only-routing-for-availability-groups/#comment-33145&quot;&gt;Louise&lt;/a&gt;.

That may be true in 2022.  I have not specifically looked at it to see.  But it is still worthwhile to review and make sure the replicas are listed in the right order and based on how you want it to behave.  If you have a replica in another data center for example, you typically wouldn&#039;t want it to receive the queries from an app server in the main data center.]]></description>
			<content:encoded><![CDATA[<p>In reply to <a href="https://sqlsolutionsgroup.com/how-to-configure-read-only-routing-for-availability-groups/#comment-33145">Louise</a>.</p>
<p>That may be true in 2022.  I have not specifically looked at it to see.  But it is still worthwhile to review and make sure the replicas are listed in the right order and based on how you want it to behave.  If you have a replica in another data center for example, you typically wouldn&#8217;t want it to receive the queries from an app server in the main data center.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Louise		</title>
		<link>https://sqlsolutionsgroup.com/how-to-configure-read-only-routing-for-availability-groups/#comment-33145</link>

		<dc:creator><![CDATA[Louise]]></dc:creator>
		<pubDate>Fri, 19 Jul 2024 02:45:34 +0000</pubDate>
		<guid isPermaLink="false">https://sqlsolutionsgroup.com/?p=6282#comment-33145</guid>

					<description><![CDATA[In reply to &lt;a href=&quot;https://sqlsolutionsgroup.com/how-to-configure-read-only-routing-for-availability-groups/#comment-20675&quot;&gt;Randy Knight&lt;/a&gt;.

But won&#039;t it do that automatically?  My testing (on SQL 2022) shows that it does.]]></description>
			<content:encoded><![CDATA[<p>In reply to <a href="https://sqlsolutionsgroup.com/how-to-configure-read-only-routing-for-availability-groups/#comment-20675">Randy Knight</a>.</p>
<p>But won&#8217;t it do that automatically?  My testing (on SQL 2022) shows that it does.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Randy Knight		</title>
		<link>https://sqlsolutionsgroup.com/how-to-configure-read-only-routing-for-availability-groups/#comment-20675</link>

		<dc:creator><![CDATA[Randy Knight]]></dc:creator>
		<pubDate>Thu, 28 Dec 2023 00:22:44 +0000</pubDate>
		<guid isPermaLink="false">https://sqlsolutionsgroup.com/?p=6282#comment-20675</guid>

					<description><![CDATA[In reply to &lt;a href=&quot;https://sqlsolutionsgroup.com/how-to-configure-read-only-routing-for-availability-groups/#comment-20673&quot;&gt;Bee&lt;/a&gt;.

Because you don&#039;t always know which replica will be PRIMARY and which will be SECONDARY/READONLY.  This way if you failover, Read-Only Routing will still work. Also, if for some reason the read-only replica(s) are not available, you want it to be routed to the primary.]]></description>
			<content:encoded><![CDATA[<p>In reply to <a href="https://sqlsolutionsgroup.com/how-to-configure-read-only-routing-for-availability-groups/#comment-20673">Bee</a>.</p>
<p>Because you don&#8217;t always know which replica will be PRIMARY and which will be SECONDARY/READONLY.  This way if you failover, Read-Only Routing will still work. Also, if for some reason the read-only replica(s) are not available, you want it to be routed to the primary.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Bee		</title>
		<link>https://sqlsolutionsgroup.com/how-to-configure-read-only-routing-for-availability-groups/#comment-20673</link>

		<dc:creator><![CDATA[Bee]]></dc:creator>
		<pubDate>Wed, 27 Dec 2023 22:55:15 +0000</pubDate>
		<guid isPermaLink="false">https://sqlsolutionsgroup.com/?p=6282#comment-20673</guid>

					<description><![CDATA[why do we need to add both the server that are part of AG to the read only routing list? I though we only the replica and not both instances.]]></description>
			<content:encoded><![CDATA[<p>why do we need to add both the server that are part of AG to the read only routing list? I though we only the replica and not both instances.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Randy Knight		</title>
		<link>https://sqlsolutionsgroup.com/how-to-configure-read-only-routing-for-availability-groups/#comment-552</link>

		<dc:creator><![CDATA[Randy Knight]]></dc:creator>
		<pubDate>Sat, 13 Mar 2021 21:15:32 +0000</pubDate>
		<guid isPermaLink="false">https://sqlsolutionsgroup.com/?p=6282#comment-552</guid>

					<description><![CDATA[In reply to &lt;a href=&quot;https://sqlsolutionsgroup.com/how-to-configure-read-only-routing-for-availability-groups/#comment-545&quot;&gt;Kobi Cohen&lt;/a&gt;.

Great point on the client side ApplicationIntent. That may be worth a follow-up post of it&#039;s own.   

Thanks for reading!]]></description>
			<content:encoded><![CDATA[<p>In reply to <a href="https://sqlsolutionsgroup.com/how-to-configure-read-only-routing-for-availability-groups/#comment-545">Kobi Cohen</a>.</p>
<p>Great point on the client side ApplicationIntent. That may be worth a follow-up post of it&#8217;s own.   </p>
<p>Thanks for reading!</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Kobi Cohen		</title>
		<link>https://sqlsolutionsgroup.com/how-to-configure-read-only-routing-for-availability-groups/#comment-545</link>

		<dc:creator><![CDATA[Kobi Cohen]]></dc:creator>
		<pubDate>Sat, 13 Mar 2021 09:27:11 +0000</pubDate>
		<guid isPermaLink="false">https://sqlsolutionsgroup.com/?p=6282#comment-545</guid>

					<description><![CDATA[Gteat post Scott.
I have 2 comments:
1. You might want to use the server IP instead of server name for routing url since if the refferencing App or user are out of the domain you might have a problem..
2. Routing will not be done unless you add &quot;ApplicationIntent=ReadOnly&quot; (it is case sensitive) to the connection string and make sure that secondary replica is readable.
But the greatest challenge here is to educate Developers, DBA, QA and etc. to properly use it (via SSMS, App and etc.) and only in connections that does only reading and not writing.
It took us a while and few presentations to do that 😀
Regards]]></description>
			<content:encoded><![CDATA[<p>Gteat post Scott.<br />
I have 2 comments:<br />
1. You might want to use the server IP instead of server name for routing url since if the refferencing App or user are out of the domain you might have a problem..<br />
2. Routing will not be done unless you add &#8220;ApplicationIntent=ReadOnly&#8221; (it is case sensitive) to the connection string and make sure that secondary replica is readable.<br />
But the greatest challenge here is to educate Developers, DBA, QA and etc. to properly use it (via SSMS, App and etc.) and only in connections that does only reading and not writing.<br />
It took us a while and few presentations to do that 😀<br />
Regards</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
