0

Migration Strategy feedback request

I am currently using the community version of Centerprise with an eye towards the professional version. I could use some practical direction on what I am trying to do in the community version and a better understanding how the professional version would make this process simpler.

What is the smartest strategy to convert the following tables? There are
identifiers that will enable me to keep track of which child record belongs
to the parent record.

*The Source Tables*


ROH - The header table
ROITEM - The child table with 0 to may records relating to the ROH
table.
There is a field value in this table that will determine
which target table the data will go in

 

*The Target Tables*


ROS - The header table
    JOBS - Another sub header table - there may be 0 to many records relating back to the ROS table
          JOBFEES - A child table with 0 to many records relating to the JOBS table
          JOBLABOR - A child table with 0 to many records relating to the JOBS table
          JOBPARTS - A child table with 0 to many records relating to the JOBS table
         JOBSUBLETS - A child table with 0 to many records relating to the JOBS table

 

I know I can create a DataFlow for each table but I would like to combine
it into one process as much as possible. I have the Parent Accounts and
Customers tables in another DataFlow working as expected thanks to your
TimeStamp function.

I also have a VEHICLES table that relates back to the ROS, JOBS, and the
JOBxx tables. Yeah poor DB design by someone else.

Thanks,
Charles

12 comments

Please sign in to leave a comment.