﻿<?xml version='1.0' encoding='UTF-8'?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/"><channel><title>SQLServerCentral / Discuss Content Posted by Chris Kempster / Article Discussions / Article Discussions by Author  / Data Migration : Step by Step / Latest Posts</title><generator>InstantForum.NET v2.9.0</generator><description>SQLServerCentral</description><link>http://www.sqlservercentral.com/Forums/</link><webMaster>notifications@sqlservercentral.com</webMaster><lastBuildDate>Mon, 20 May 2013 11:45:17 GMT</lastBuildDate><ttl>20</ttl><item><title>RE: Data Migration : Step by Step</title><link>http://www.sqlservercentral.com/Forums/Topic3066-75-1.aspx</link><description>&lt;P&gt;&lt;SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: Verdana"&gt;I think that it was a worthwhile attempt to set out procedures for a task like this.  But, honestly, I found it a bit difficult to follow.  Every case is different, some models evolve, other need to run to strict frameworks.  I work by the evolution model myself.  I take more time over it, but there are less staff involved.  I am trying to summarise the main points from my view.&lt;?xml:namespace prefix = o ns = "urn:schemas-microsoft-com:office:office" /&gt;&lt;o:p&gt;&lt;/o:p&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: Verdana"&gt;1. All data sources should be recorded.  Either that or the original raw data should be kept.&lt;o:p&gt;&lt;/o:p&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: Verdana"&gt;2. All code that alters this data should be kept.  In my case this is either Perl code or T-SQL code, in the form of SPROCs.&lt;o:p&gt;&lt;/o:p&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: Verdana"&gt;If the above is done sensibly, in both file directories and databases,  why worry?&lt;o:p&gt;&lt;/o:p&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: Verdana"&gt;I have a few other tips.&lt;o:p&gt;&lt;/o:p&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: Verdana"&gt;1.  Keep a log of errors that everybody has access to.&lt;o:p&gt;&lt;/o:p&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: Verdana"&gt;2.  Name the different versions of the system that is being implemented.&lt;o:p&gt;&lt;/o:p&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: Verdana"&gt;3.  Keep all involved through the use of email updates, one for each major new release.&lt;o:p&gt;&lt;/o:p&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: Verdana"&gt;4.  Keep testing/using the system with real life data requests.&lt;o:p&gt;&lt;/o:p&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: Verdana"&gt;5.  Separate the development of the user interface (in my case an Excel VBA application), the request file handling systems (Perl based) and the analytical database (MS SQL Server)&lt;o:p&gt;&lt;/o:p&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: Verdana"&gt;6.  Enable a record of all results that have been returned to users.&lt;o:p&gt;&lt;/o:p&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P class=MsoNormal style="MARGIN: 0cm 0cm 0pt"&gt;&lt;FONT size=3&gt;&lt;FONT face="Times New Roman"&gt; &lt;o:p&gt;&lt;/o:p&gt;&lt;/FONT&gt;&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt; &lt;/P&gt;</description><pubDate>Mon, 27 Nov 2006 09:47:00 GMT</pubDate><dc:creator>Mark Green</dc:creator></item><item><title>RE: Data Migration : Step by Step</title><link>http://www.sqlservercentral.com/Forums/Topic3066-75-1.aspx</link><description>&lt;P&gt;Well done document, it was worth my time.  I will use it as guideline as such projects may evolve down the road.&lt;/P&gt;&lt;P&gt;Nice job!!  &lt;img src='images/emotions/smile.gif' height='20' width='20' border='0' title='Smile' align='absmiddle'&gt;&lt;/P&gt;</description><pubDate>Mon, 28 Nov 2005 07:08:00 GMT</pubDate><dc:creator>ivan gonzalez-195804</dc:creator></item><item><title>RE: Data Migration : Step by Step</title><link>http://www.sqlservercentral.com/Forums/Topic3066-75-1.aspx</link><description>&lt;P&gt;A very welcome article - even for smaller migrations it will be very useful as a template. &lt;/P&gt;&lt;P&gt;Can you indicate at which stage you would address differences in collation order, and the requirements for login permissions of the new system?&lt;/P&gt;</description><pubDate>Mon, 28 Nov 2005 06:23:00 GMT</pubDate><dc:creator>mosaic-263591</dc:creator></item><item><title>RE: Data Migration : Step by Step</title><link>http://www.sqlservercentral.com/Forums/Topic3066-75-1.aspx</link><description>I will have to read it for content, in greater detail, but after a second pass I can already see things I would have overlooked if I had been doing it... not a bad template / starting point</description><pubDate>Fri, 25 Mar 2005 19:05:00 GMT</pubDate><dc:creator>Howard_nyc@yahoo.com</dc:creator></item><item><title>Data Migration : Step by Step</title><link>http://www.sqlservercentral.com/Forums/Topic3066-75-1.aspx</link><description>Comments posted to this topic are about the content posted at &lt;A HREF=http://www.sqlservercentral.com/columnists/ckempster/datamigrationoverview.asp&gt;http://www.sqlservercentral.com/columnists/ckempster/datamigrationoverview.asp&lt;/A&gt;</description><pubDate>Sun, 17 Mar 2002 00:00:00 GMT</pubDate><dc:creator>ckempste</dc:creator></item></channel></rss>