Page 1 of 1

Teradata BTEQ to Vertica - migration

Posted: Thu Feb 28, 2013 1:12 pm
by migration_guru
Hello All
I am working on a POC to migrate Teradata to Vertica, and specifically interested to know if anyone has prior experience in converting Teradata BTEQ scripts and Stored procedures to equivalent Vertica scripts. Any pointers will be very helpful.

Which one works best with Vertica ?

BTEQ --> Python Vertica
BTEQ --> Perl Vertica
BTEQ --> Java Vertica
??
??

Thanks
Rav

Re: Teradata BTEQ to Vertica - migration

Posted: Sat Mar 02, 2013 9:10 am
by id10t
Hi!

1. Python
2. Java
###
3. Perl - out of list (... why not BrainFack? :) )
  • By dependencies out of box: Python - OK; Java require JVM (Python comes with Vertica)
  • Connect to Vertica : Python - require unixODBC, pyODBC; Java - JVM only (drivers comes with Vertica)
  • License: Python - OK; Java - proprietary(ORACLE)
  • Dev: Python - easy(+++), Java - robust/stable/standard
PS:
As generic module - Java (after it easy port to Jython/Python, Scala), adapt to Hadoop
As solution for specific problem - Python

Re: Teradata BTEQ to Vertica - migration

Posted: Sun Mar 03, 2013 4:58 am
by migration_guru
Thank you. Atleast now i know there ain't anything simple like Oracle sql*plus or Teradata bteq.
Any sample code snippets will be helpful.

Vertica Dev team :
Any plans in the near future to make our life simpler ;)

Re: Teradata BTEQ to Vertica - migration

Posted: Sun Mar 03, 2013 8:42 am
by id10t
Hi!

You need 3 main modules - parser, lexer and worker. Most difficult part is - lexer(a lexical analysis), since syntax already defined.
If you are not guru in BTEQ or SQL*Plus - you will fail in lexical analysis.

>> Any sample code snippets will be helpful.
For what language? What is your design choice for db connector - Proxy, Mediator? What is your main design pattern - ORM, Interpreter ?