<?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: A Faster Way to Migrate SQL Server Instances!	</title>
	<atom:link href="https://sqlsolutionsgroup.com/migrate-sql-server/feed/" rel="self" type="application/rss+xml" />
	<link>https://sqlsolutionsgroup.com/migrate-sql-server/</link>
	<description></description>
	<lastBuildDate>Tue, 07 Jul 2026 23:03:22 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=7.0.2</generator>
	<item>
		<title>
		By: tom		</title>
		<link>https://sqlsolutionsgroup.com/migrate-sql-server/#comment-69</link>

		<dc:creator><![CDATA[tom]]></dc:creator>
		<pubDate>Thu, 05 Nov 2020 09:06:50 +0000</pubDate>
		<guid isPermaLink="false">http://sqlsolutionsgroup.com/?p=2068#comment-69</guid>

					<description><![CDATA[Hi Mike, this is a nice and helpful article, but i disagree in two points:
1. IMHO you list methods, not methodologies
2. i was looking for a way of migrating a whole instance in one single step, but you write about a database by database migration.

And a comment to method #5: this is similar to just moving the physical disks from the old to the new server (as we used to do when there was/is no SAN).

But anyway - this is a good starting point for figuring out a personal way of getting a migration job done. Thanks for sharing!
-tom
ps: there might be a typo in the script in line 29: is it really &#039;ditribution&#039; (and not &#039;distribution&#039;)?]]></description>
			<content:encoded><![CDATA[<p>Hi Mike, this is a nice and helpful article, but i disagree in two points:<br />
1. IMHO you list methods, not methodologies<br />
2. i was looking for a way of migrating a whole instance in one single step, but you write about a database by database migration.</p>
<p>And a comment to method #5: this is similar to just moving the physical disks from the old to the new server (as we used to do when there was/is no SAN).</p>
<p>But anyway &#8211; this is a good starting point for figuring out a personal way of getting a migration job done. Thanks for sharing!<br />
-tom<br />
ps: there might be a typo in the script in line 29: is it really &#8216;ditribution&#8217; (and not &#8216;distribution&#8217;)?</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Jason Brimhall		</title>
		<link>https://sqlsolutionsgroup.com/migrate-sql-server/#comment-68</link>

		<dc:creator><![CDATA[Jason Brimhall]]></dc:creator>
		<pubDate>Wed, 07 Mar 2018 02:36:37 +0000</pubDate>
		<guid isPermaLink="false">http://sqlsolutionsgroup.com/?p=2068#comment-68</guid>

					<description><![CDATA[In reply to &lt;a href=&quot;https://sqlsolutionsgroup.com/migrate-sql-server/#comment-67&quot;&gt;James&lt;/a&gt;.

I disagree. The entire premise of the article is about migrating or upgrading an instance. While this does include the migration of databases, it is only a step in the process of migrating the instance which is discussed in the article too.]]></description>
			<content:encoded><![CDATA[<p>In reply to <a href="https://sqlsolutionsgroup.com/migrate-sql-server/#comment-67">James</a>.</p>
<p>I disagree. The entire premise of the article is about migrating or upgrading an instance. While this does include the migration of databases, it is only a step in the process of migrating the instance which is discussed in the article too.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: James		</title>
		<link>https://sqlsolutionsgroup.com/migrate-sql-server/#comment-67</link>

		<dc:creator><![CDATA[James]]></dc:creator>
		<pubDate>Thu, 22 Feb 2018 15:55:33 +0000</pubDate>
		<guid isPermaLink="false">http://sqlsolutionsgroup.com/?p=2068#comment-67</guid>

					<description><![CDATA[Good information, but this is not &quot;Migrating Instances&quot;. Its more appropriately named &quot;Migrating Databases&quot;.]]></description>
			<content:encoded><![CDATA[<p>Good information, but this is not &#8220;Migrating Instances&#8221;. Its more appropriately named &#8220;Migrating Databases&#8221;.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Yasir		</title>
		<link>https://sqlsolutionsgroup.com/migrate-sql-server/#comment-66</link>

		<dc:creator><![CDATA[Yasir]]></dc:creator>
		<pubDate>Tue, 20 Sep 2016 07:04:59 +0000</pubDate>
		<guid isPermaLink="false">http://sqlsolutionsgroup.com/?p=2068#comment-66</guid>

					<description><![CDATA[Hi Mike,
 very nice article.
I have one question.

We are planning to migrate sql server instances from one DC to another DC 500 Kms apart.
We are going for SAN replication.
On source SAN is HP and it may or it may not be  HP in target.

What are the options to migrate sql instances in new DC?

Regards,]]></description>
			<content:encoded><![CDATA[<p>Hi Mike,<br />
 very nice article.<br />
I have one question.</p>
<p>We are planning to migrate sql server instances from one DC to another DC 500 Kms apart.<br />
We are going for SAN replication.<br />
On source SAN is HP and it may or it may not be  HP in target.</p>
<p>What are the options to migrate sql instances in new DC?</p>
<p>Regards,</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
