Is the table prebuilt on the $dest DB? Any concerns with encoding? Differing data types? Large amounts of space?

If not, why not something as simple as:

  1. start transaction on $dest
  2. Start cursor on $source (select * from source_table)
  3. delete data on $dest (delete from backup_table)
  4. insert each row from $source to $dest (get from $source, save to $dest)
  5. end transaction on $dest

This won't be terribly fast if it is a large table. There may also be better tools for this (export to a CSV, import from CSV, for example, given the right format of the data).

Are there any special constraints on your problem that stop you from using the straightforward solution?

--MidLifeXis


In reply to Re: Cross platform database table backup/restore by MidLifeXis
in thread Cross platform database table backup/restore by gwhite

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.