SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Data Migration : Step by Step


Data Migration : Step by Step

Author
Message
ckempste
ckempste
SSCrazy
SSCrazy (2.4K reputation)SSCrazy (2.4K reputation)SSCrazy (2.4K reputation)SSCrazy (2.4K reputation)SSCrazy (2.4K reputation)SSCrazy (2.4K reputation)SSCrazy (2.4K reputation)SSCrazy (2.4K reputation)

Group: General Forum Members
Points: 2353 Visits: 1
Comments posted to this topic are about the content posted at http://www.sqlservercentral.com/columnists/ckempster/datamigrationoverview.asp


Chris Kempster
www.chriskempster.com
Author of "SQL Server Backup, Recovery & Troubleshooting"
Author of "SQL Server 2k for the Oracle DBA"
Howard_nyc@yahoo.com
Howard_nyc@yahoo.com
Forum Newbie
Forum Newbie (4 reputation)Forum Newbie (4 reputation)Forum Newbie (4 reputation)Forum Newbie (4 reputation)Forum Newbie (4 reputation)Forum Newbie (4 reputation)Forum Newbie (4 reputation)Forum Newbie (4 reputation)

Group: General Forum Members
Points: 4 Visits: 1
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



mosaic-263591
mosaic-263591
SSC-Addicted
SSC-Addicted (467 reputation)SSC-Addicted (467 reputation)SSC-Addicted (467 reputation)SSC-Addicted (467 reputation)SSC-Addicted (467 reputation)SSC-Addicted (467 reputation)SSC-Addicted (467 reputation)SSC-Addicted (467 reputation)

Group: General Forum Members
Points: 467 Visits: 566

A very welcome article - even for smaller migrations it will be very useful as a template.

Can you indicate at which stage you would address differences in collation order, and the requirements for login permissions of the new system?


ivan gonzalez-195804
ivan gonzalez-195804
SSC Journeyman
SSC Journeyman (94 reputation)SSC Journeyman (94 reputation)SSC Journeyman (94 reputation)SSC Journeyman (94 reputation)SSC Journeyman (94 reputation)SSC Journeyman (94 reputation)SSC Journeyman (94 reputation)SSC Journeyman (94 reputation)

Group: General Forum Members
Points: 94 Visits: 1

Well done document, it was worth my time. I will use it as guideline as such projects may evolve down the road.

Nice job!!


Mark Green
Mark Green
Old Hand
Old Hand (351 reputation)Old Hand (351 reputation)Old Hand (351 reputation)Old Hand (351 reputation)Old Hand (351 reputation)Old Hand (351 reputation)Old Hand (351 reputation)Old Hand (351 reputation)

Group: General Forum Members
Points: 351 Visits: 1

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.

1. All data sources should be recorded. Either that or the original raw data should be kept.

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.

If the above is done sensibly, in both file directories and databases, why worry?

I have a few other tips.

1. Keep a log of errors that everybody has access to.

2. Name the different versions of the system that is being implemented.

3. Keep all involved through the use of email updates, one for each major new release.

4. Keep testing/using the system with real life data requests.

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)

6. Enable a record of all results that have been returned to users.


Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search