<?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: Using Aliases with SQL Server</title>
	<atom:link href="http://www.allenkinsel.com/archive/2010/01/using-aliases-in-sql-server/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.allenkinsel.com/archive/2010/01/using-aliases-in-sql-server/</link>
	<description>SQL Server, PASS, and other data mishaps</description>
	<lastBuildDate>Thu, 22 Jul 2010 13:53:20 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Ken</title>
		<link>http://www.allenkinsel.com/archive/2010/01/using-aliases-in-sql-server/comment-page-1/#comment-87</link>
		<dc:creator>Ken</dc:creator>
		<pubDate>Tue, 16 Feb 2010 21:57:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.allenkinsel.com/?p=147#comment-87</guid>
		<description>I&#039;m currently in a migration that will be making use of dns aliases, and have done some testing of moving from a default instance to named instances.  You actually can use this still for moving applications from one named instance to another, you have to configure your named instances to listen on the default port 1433.  If your named instances listen on 1433 you can connect to them via your alias without specifying the instance name.  If these instances reside on the same server, they will need to listen on their own ip addresses so both can use 1433.

The ability to omit the instance name when connecting to an instance listening on 1433 using a dns alias does not appear to work with SQL 2000 client, only 2005 and newer.</description>
		<content:encoded><![CDATA[<p>I'm currently in a migration that will be making use of dns aliases, and have done some testing of moving from a default instance to named instances.  You actually can use this still for moving applications from one named instance to another, you have to configure your named instances to listen on the default port 1433.  If your named instances listen on 1433 you can connect to them via your alias without specifying the instance name.  If these instances reside on the same server, they will need to listen on their own ip addresses so both can use 1433.</p>
<p>The ability to omit the instance name when connecting to an instance listening on 1433 using a dns alias does not appear to work with SQL 2000 client, only 2005 and newer.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Allen Kinsel</title>
		<link>http://www.allenkinsel.com/archive/2010/01/using-aliases-in-sql-server/comment-page-1/#comment-52</link>
		<dc:creator>Allen Kinsel</dc:creator>
		<pubDate>Thu, 21 Jan 2010 22:10:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.allenkinsel.com/?p=147#comment-52</guid>
		<description>Yes,  this is exactly describing using a CNAME record in the DNS Server but, you can also use a Host(A) record and point directly back to the IP adress.  In our environment, I dont have any say in that matter and we use new Host(A) records pointed directly to IP&#039;s.  I dont think it really matters but, you&#039;re absolutely right Aliases make moves simple.</description>
		<content:encoded><![CDATA[<p>Yes,  this is exactly describing using a CNAME record in the DNS Server but, you can also use a Host(A) record and point directly back to the IP adress.  In our environment, I dont have any say in that matter and we use new Host(A) records pointed directly to IP's.  I dont think it really matters but, you're absolutely right Aliases make moves simple.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Todd McDermid</title>
		<link>http://www.allenkinsel.com/archive/2010/01/using-aliases-in-sql-server/comment-page-1/#comment-51</link>
		<dc:creator>Todd McDermid</dc:creator>
		<pubDate>Thu, 21 Jan 2010 21:29:17 +0000</pubDate>
		<guid isPermaLink="false">http://www.allenkinsel.com/?p=147#comment-51</guid>
		<description>I&#039;m not a network guy - but is this what is also referred to as a CNAME?  

If so - I&#039;m doing this exactly, and it helped us seamlessly move databases off of a misconfigured machine with a minimum of downtime and NO app changes.  Without CNAMEs, it would have either taken much more downtime, had to have been done piecemeal, and/or would have resulted in apps breaking because we &quot;missed&quot; an obscure configuration setting.

We have a CNAME for each atomic set of databases that we want kept together.  Sometimes that means multiple CNAMEs point to the same physical machine, sometimes not.

Works great - no drawbacks so far!</description>
		<content:encoded><![CDATA[<p>I'm not a network guy - but is this what is also referred to as a CNAME?  </p>
<p>If so - I'm doing this exactly, and it helped us seamlessly move databases off of a misconfigured machine with a minimum of downtime and NO app changes.  Without CNAMEs, it would have either taken much more downtime, had to have been done piecemeal, and/or would have resulted in apps breaking because we &laquo;missed&raquo; an obscure configuration setting.</p>
<p>We have a CNAME for each atomic set of databases that we want kept together.  Sometimes that means multiple CNAMEs point to the same physical machine, sometimes not.</p>
<p>Works great - no drawbacks so far!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jorge Segarra</title>
		<link>http://www.allenkinsel.com/archive/2010/01/using-aliases-in-sql-server/comment-page-1/#comment-50</link>
		<dc:creator>Jorge Segarra</dc:creator>
		<pubDate>Thu, 21 Jan 2010 14:53:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.allenkinsel.com/?p=147#comment-50</guid>
		<description>Awesome, great timing as this is the exact solution I just implemented thanks to you and the rest of the SQL tweeps via the the #sqlhelp tag. Thanks again!</description>
		<content:encoded><![CDATA[<p>Awesome, great timing as this is the exact solution I just implemented thanks to you and the rest of the SQL tweeps via the the #sqlhelp tag. Thanks again!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
