VerticaZvika GutkinDB ExpertZvika.gutkin@gmail.com
Loading – Best practices
Loading – Best practices
Loading – Best practices
Loading – Best practices
Loading – Best practices
Loading – Best practices• Avoid using update & delete   – Can Only be serial transaction   – Update in Vertica is delete +...
Loading – Best practices• COPY FROM STDIN pipes from STDIN  zcat table_a.gzip | vsql –c “COPY table_a from STDIN DIRECT;”•...
Loading – Best practices• Do not use Vertica map reducer plugin• Do not use fuse• Use Liveperson’s generic loading infrast...
Questions
Thank You
Upcoming SlideShare
Loading in …5
×

Vertica loading best practices

6,776 views

Published on

Presentation i gave to developers .
Basic rules on what to do and what not to do.

  • Be the first to comment

Vertica loading best practices

  1. 1. VerticaZvika GutkinDB ExpertZvika.gutkin@gmail.com
  2. 2. Loading – Best practices
  3. 3. Loading – Best practices
  4. 4. Loading – Best practices
  5. 5. Loading – Best practices
  6. 6. Loading – Best practices
  7. 7. Loading – Best practices• Avoid using update & delete – Can Only be serial transaction – Update in Vertica is delete + insert .• Do not load more than 50 files per load. – Vertica Limitation.• Use copy direct for large inserts – Will bypass the WOS.• Use INSERT /*+DIRECT*/ • Will bypass the WOS.
  8. 8. Loading – Best practices• COPY FROM STDIN pipes from STDIN zcat table_a.gzip | vsql –c “COPY table_a from STDIN DIRECT;”• Use Vertica ability to load from gzip files.• Use Parallel load – multiple separate COPY commands that load different files from different nodes. – Issue a single multi-node COPY command **
  9. 9. Loading – Best practices• Do not use Vertica map reducer plugin• Do not use fuse• Use Liveperson’s generic loading infrastructure.
  10. 10. Questions
  11. 11. Thank You

×