I tend to agree with voyager and your coworkers on this one: if the job is as big as it sounds, use SQL to do the job. As soon as you start using tools external to the DBMS to start manipulating large sets of data, the speed at which the manipulation occurs is greatly decreased. While I find that DBI is pretty quick and flexible, it can never match the speed at which you can run SQL at the server console (well, at least not that I've seen!)

It certainly is nice to use/want to use perl for the manipulation, but most DBMSes that I've seen these days have some pretty decent functions for manipulating and transforming data.

Just my two bits. Hope it is some use.
MrCromeDome

In reply to Re: Data Migration Perl style vs. SQL style.... by MrCromeDome
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.