|Type of Support||
Read & Write, In-Database
Database Version: 9.3.1-0
Alteryx Tools Used to Connect
Standard Workflow Processing
In-Database Workflow Processing
Beginning with 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 Vertica 6 as a 65,000 byte "varbinary" field. In 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 Vertica version supports.
- Long Varchar: Vertica 6 supports strings up to 65,000 bytes wide (varchar) and 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 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.
Extended ASCII characters in Latin I in a string or v_string are 1-byte characters in Alteryx. Vertica expects to receive all text data in UTF-8. Extended ASCII characters in Latin I in a string or v_string are considered 1-byte characters in Alteryx, but are 2-byte characters in UTF-8.If a string or v_string field created with a Data Output tool to an HP Vertica database is too small to contain the 2-byte version of the characters, a truncation error results when attempting to write data in this field to the database. To avoid this, use w_string or vw_string fields or increase the size of the string field to allow for the additional bytes.