Re: Optimization of data migration

Tech-Archive recommends: Fix windows errors by optimizing your registry

To move the data you will need to understand the differences between DB2 and
SQL Server. The ranges stored in datatypes may be different, there may be
completely incompatable datatypes. The list that I gave you will help to
optimise the load. What it will not do is tell you the differences between
SQL Server and DB2. This article does it in reverse though

http://www.redbooks.ibm.com/tstudio/dataware/migrate/index_4.htm






"fleo" <fleo@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:80BB64EE-83F3-4D66-B7AF-614FF4EE80D3@xxxxxxxxxxxxxxxx
> Yes I need to perform cleaning/transformation.
>
> All the info I found put the emphasis on migrating the database itself
> rather than the data. Do you know where I could get information about
> migrating the data? The pitfalls, the things I should check in the source
> data, how to design the DTS to be able to go from developpement to test
> and
> production phases, ...
>
> Thank you
>
> "Allan Mitchell" wrote:
>
>> It could well be worthwhile having a staging area yes. This way your
>> data
>> can go through a series of screens to clean things up and when it reaches
>> the end of the process is ready for insertion into the real destination.
>>
>> do you need to do cleansing or is it a stright pick up and move?
>>
>>
>> Allan
>>
>>
>> "fleo" <fleo@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
>> news:62DC12EE-AC4C-4543-905A-F16257FB6C6D@xxxxxxxxxxxxxxxx
>> > "Allan Mitchell" wrote:
>> >
>> >> A few things that run off the top of my head.
>> >>
>> >> Make sure that you have the appropriate indexes on the Source to
>> >> facilitate retrieval of the data to move,
>> >> When inserting to the destination removes indexes and triggers.
>> >> Move only the data you ctually need to move
>> >> Fast Disks
>> >> Fast CPUs + cache
>> >> As little distance as possible betwen Source And Destination (fast
>> >> Network)
>> > Thanks Allan.
>> >
>> > I found papers on migrating from Oracle, MySQL, ... but nothing on
>> > DB2??
>> > (http://www.microsoft.com/technet/interopmigration/sql.mspx)
>> >
>> > I am going to be migrating the data only (not the objects). I have
>> > seen
>> > multiple options and I am not sure about the best way to go. Should I
>> > create
>> > a staging database?
>>
>>
>>


.

Relevant Pages

  • Re: Optimization of data migration
    ... I read the article and got puzzled by the "source physical file". ... something equivalent when migrating to SQL Server? ... database and copy the data "as is" in a staging database. ...
    (microsoft.public.sqlserver.dts)
  • Re: Guide for switching to .ADP from .MDB
    ... If I am correct then you are opting for this option in migrating the ... Create an Access database front-end to an SQL Server database back-end ...
    (microsoft.public.access.adp.sqlserver)
  • Importing updated data in SQL2000
    ... I'm migrating an ACCESS DB to SQL server 2000. ... Now I'm migrating all the code, ... relations and keys. ... append new data and also overwrite the existing one. ...
    (microsoft.public.sqlserver.dts)
  • Ms ACCESS, SQL SERVER AND MERGE REPLICATION.
    ... I am in testing phase of migrating ... been created and when i published database for replication on ... but i donot understand all the four coloum that has been ... When i migrate to sql server table become like this ...
    (microsoft.public.sqlserver.programming)
  • rexx to perl
    ... and now it need to be migrating /porting on AIX, perl with DB2 some new ... and most scrips covered databse related features. ...
    (comp.unix.questions)