Re: Optimization of data migration

Many thanks for your help Alan!
I read the article and got puzzled by the "source physical file". Is there
something equivalent when migrating to SQL Server?

I am definitely not an expert on DTS so maybe I'm missing something and
being too simplistic. I had in mind to create an OLEDB connection to the DB2
database and copy the data "as is" in a staging database. Maybe I could
perform some sort of filtration at the same time??

Then I would transform/copy the data to the real database...

"Allan Mitchell" wrote:

> 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: 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)
  • Re: Moving to MS SQL
    ... Personally-- I thnk that RAID5 should be reliable enough. ... One additional major point is security: SQL Server can be much more ... Availability also has other aspects, such as redundancy, database ... migrating to SQL Server. ...
    (microsoft.public.access.adp.sqlserver)
  • Re: Importing oracle database into sql server 2000
    ... for migrating data to another database platform. ... Chapter from the SQL Server Resource Kit: ... Chapter 7 - Migrating Oracle Databases to SQL Server 2000 ...
    (microsoft.public.sqlserver.dts)
  • Access97 / 200x Migration
    ... Need help in understanding what is involved in migrating from Access97 to ... I am a self-taught programmer ... everything under a single database, it has a different database for each ... I want to get into SQL server. ...
    (microsoft.public.access.modulesdaovba)
  • Re: restore MSSQL 7 backup to MSSQL 2000?
    ... Migrating from 7.0 to 2000 is fully supported. ... You cannot restore or attach a SQL Server 2000 databaes to SQL Server 7. ... > problems migrating a 7 database to a 2000 version. ... > "Keith Kratochvil" wrote: ...
    (microsoft.public.sqlserver.server)