If the transformations are complicated (i.e., require a lot of procedural logic) and the datasets are relatively small, go ahead and use Perl.

But if the transformations are straight forward and the datasets are large, use SQL. The SQL engine knows how do deal with large amounts of data, can do joins, sorts, etc. all very fast even on large amounts of data. I'd use SQL for all that I could and use Perl for any scripting or procedural logic.

And if you have non-Perl folks involved, using SQL tables as staging areas allows the data to be viewed/verified with what ever tools you have, e.g. Crystal, or any iSQL tool.

In reply to Re: Data Migration Perl style vs. SQL style.... by voyager
in thread Data Migration Perl style vs. SQL style.... by mr.dunstan

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.