Just think about this: to move a table across the network
you can either (a) make a physical copy, and this includes
data, indexes, triggers, transaction caches, and whatever
the DBMS keeps in store for that table, or (b) copy just
the data as SQL statements or as exportable text, but then
the receiving DBMS should rebuild the indexes.
Instead, to calculate a CRC you have just a table scan.
Therefore you should compare the time needed to calculate
a SHA twice per record (one for the record and one to apply
it to a global SHA) versus the time needed to pass all the
above mentioned stuff over the network.
I put my bet on SHA. :)
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.