âShow Table of Contents
|Type of Support
||Read & Write; In-Database
||Database version 6.1.3, 7.0.1, 8.0.1
ODBC client version 6.1.3, 7.0.1, 8.0.1
||ODBC (32- and 64-bit)
||The ODBC driver can be downloaded from HP Vertica.
In-Database processing requires 64-bit database drivers.
Alteryx tools used to connect:
Beginning with HP Vertica 7, two additional data types are supported:
- Long VarBinary: Alteryx uses this data type when a blob/spatial field is wider than 65,000 bytes and up to 32,000,000 bytes. (Version 6 supports a maximum of 65,000 bytes of blob data). If a larger blob is passed through, Alteryx writes a null value and reports a conversion error. Alteryx does not truncate a blob value.
You cannot specify the width of a blob field in Alteryx. (Setting a width in a Select Tool has no effect.) A blob field is written to HP Vertica 6 as a 65,000 byte "varbinary" field. In HP Vertica 7, it is written as a 32,000,000 byte "long varbinary" field. Since they are both variable data types, Alteyrx specifies the maximum width the HP Vertica version supports.
- Long Varchar: HP Vertica 6 supports strings up to 65,000 bytes wide (varchar) and HP Vertica version 7 supports strings up to 32,000,000 bytes wide (long varchar).
- Alteryx currently only supports 16,777,216 bytes (octets) per string. An octet is the number of bytes it takes to hold a character. (For multi-byte character sets, this can be three bytes per character.) This limitation only exists in the ODBC code.
- Alteryx uses "varchar" in HP Vertica if the string field size is 65,000 bytes or less. Starting with HP Vertica 7, if the string is wider than 65,000 bytes, Alteryx uses "long varchar." Alteryx truncates strings to their maximum width and reports conversion errors if truncation occurs.
Â©2017 Alteryx, Inc., all rights reserved. AllocateÂ®, AlteryxÂ®, GuzzlerÂ®, and SolocastÂ® are registered trademarks of Alteryx, Inc.