User Guide : Map Connectors : Source and Target Map Connectors : Actian Avalanche Multimode
 
Share this page             
Actian Avalanche Multimode
Actian Avalanche is a fully managed cloud data warehouse delivered as a service. It is a database application that you can connect natively to through ODBC 3.5. For more information, see Actian Avalanche documentation available at docs.actian.com.
The multimode connector allows you to read, write, or append data to multiple tables at one time within one map.
The integration platform connects to Actian Avalanche tables through ODBC 3.5.
Prerequisites
Install Actian Avalanche client runtime. Go to esd.actian.com and download the required version of Actian Avalanche.
For the installation details, see Actian Avalanche client documentation available at docs.actian.com.
Setup ODBC Data Source for Avalanche. For the steps, see Prerequisites in Actian Avalanche section.
Connector Properties
You can set the following target properties.
Property
S/T
Description
Encoding
T
Type of encoding to use with source and target files. The default value is OEM.
SQL Output
T
Output mode for SQL statements. There are four output modes:
Target Only (default) - Uses bound mode, which uses bind variables. SQL statements are sent to the Target and not to the SQL log specified in the SQL Log property.
Target Only (Unbound mode) - Uses unbound mode, which does not use bind variables and sends the literal SQL statement to the database engine. SQL statements are sent to the Target and not to the SQL log specified in the SQL Log property.
Target and SQL Log - Sends SQL statements to the Target and to the SQL log specified in the SQL Log property.
SQL Log Only - Sends SQL statements only to the SQL log file specified in the SQL Log property.
Note:  Bound mode is faster since bind variables are used.
SQL Log
T
SQL log file in the default installation directory. The default file name is sql.log. To use a different log, browse to the file or enter the path and file name.
UpdateNullfields
T
If set to True, null values are sent to the database when inserting or updating records.
If set to False, null values are not sent to the database when inserting or updating records. Also, this property forces the connector to operate in unbound mode, which may cause slower performance.
The default value is False.
Best Practice — If fields in the target record are not mapped, then the null values are passed to the target. If you do not want to write to these fields, then it is recommended to set the value for UpdateNullFields to False.
SystemTables
T
If set to True, allows you to see all tables created by the Database Administrator (DBA) in the database. The system table names appear in the table list. The default value is False.
Note:  This property is applicable only if you have logged in to the database as the DBA. Only the DBA has access to system tables.
Views
T
If set to True, this property allows you to see the view names in the table list along with the table names. Default is True.
Note:  This property supports only Append and DeleteAndAppend output modes and does not support the Replace output mode.
Synonyms
T
If set to True this property allows you to see synonyms. The alias names appear in the table list along with the tables. Default is false.
DSNType
T
Data sources or drivers to connect to in the Data Source Name (DSN) list. DSNs are listed in Control Panel > Administrative Tools > ODBC Data Source Administrator window. The options are:
User: Created for a specific user. DSN information is stored in the registry.
System: Can be used by anyone who has access to the machine. DSN information is stored in the registry.
User & System: This is the default option.
For more information, see Configuring ODBC Data Source.
AutoCommit
T
Automatically commit changes as they are made by each SQL statement, instead of waiting until the end of the transaction. If this option is set to true, you cannot roll back the changes after they are done. The default value is false.
DriverCompletion
T
Allows you to control whether or not the driver prompts you for information. The options available are Prompt, Complete (default), Complete Required and No Prompt. The Prompt option prompts you for every individual bit of information. Complete prompts you for any information they forgot to enter. The Complete Required option prompts you only for information that is essential to complete the connection. The No Prompt option does not prompt you for any information.
IdentifierQuotes
T
Quoted identifiers are used to parse the SQL statement and distinguish between columns and character data in SQL statements. All databases have quoted identifiers.
In a SQL statement, you must enclose identifiers containing special characters or match keywords in identifier quote characters; (also known as delimited identifiers in SQL-92). For example, the Accounts Receivable identifier is quoted in the following SELECT statement:
SELECT * FROM "Accounts Receivable"
If you do not use identifier quotes, the parser assumes there are two tables, Accounts and Receivable and return a syntax error that they are not separated by a comma.
IdentifierQuotes has four options:
Default
None
"
'
ModifyDriverOptions
T
Allows you to store the ODBC connection. The default is true. If you set this to false, you are prompted for your connection information each time you run the transformation.
DriverOptions
T
Default is empty for a new map. This property will be automatically populated with ODBC connect string upon successful connection.
For ODBC connectors, the map saved database information in the Driver Option property with real values (not using macros) during the last successful connection. If you want to run the map with a different database server, you have to delete the value for Driver Option and use the correct macros for the connection information. The map repopulates the value of Driver Option when it successfully connects to the new database server.
MaxDataLength
T
Maximum number of characters to write to a field. It is the maximum data length for long data types. The default value is 1 MB. You can change this value based on the available memory and target requirements.
When this connector requests the column field size for these data types, it checks for a returned value greater than the MaxDataLength value. If the value is greater, then the MaxDataLength value is used.
Some ODBC drivers have maximum data length limitations. If you choose an ODBC source or target connector and the default setting is not 1 MB, the integration platform sets the value for that particular ODBC driver. In this case, do not set the MaxDataLength property to a higher value.
TransactionIsolation
T
Allows you to specify an isolation level when reading from or writing to a database table with ODBC. The isolation levels are:
Read uncommitted – Permits P1, P2, and P3.
Read committed – Permits P2 and P3. Does not permit P1.
Repeatable read – Permits P3. Does not permit P1 and P2.
Serializable – Does not permit P1, P2 or P3.
The default is serializable.
The ANSI SQL 2 standard defines three specific ways in which serializability of a transaction may be violated: P1 (Dirty Read), P2 (Nonrepeatable Read), and P3 (Phantoms).
For further details about TransactionIsolation levels, see the IBM DB2 Universal Database ODBC documentation.
UsePartition
T
If set to True, the WITH PARTITION=(...) clause is added to SQL statement when creating a table. The (...) is partitioning scheme that is specified in the Partition option.
If set to False, the WITH NOPARTITION clause is added to SQL statement when creating a table
The default value is False.
Partition
T
Partitioning scheme. A table partition definition format is:
PARTITION = (dimension)
The syntax for each partition dimension is:
dimension = rule ON column {, column} partitionspec {, partitionspec}| rule partitionspec {, partitionspec}
where:
rule: Defines the type of distribution scheme for assigning rows to partitions. The only valid value is HASH, which distributes rows evenly among the partitions according to a hash value.
ON column {, column}: Specifies the columns to partition the table on.
partitionspec: When rule is HASH, defines the number of partitions and optionally their names:
partitionspec = DEFAULT PARTITIONS | [nn] PARTITION[S] [(name {, name})] [with_clause]
where:
DEFAULT PARTITIONS: Uses the number of partitions specified in the DBMS configuration parameter default_npartitions. The statement returns an error if the default partition value is not set. If DEFAULT PARTITIONS is specified, neither explicit partition names nor a with_clause can be specified.
nn: Number of partitions, which defaults to 1 if omitted.
name: Identifies the partition. When the number of partitions is two or more, a comma-separated list of names can be provided to override the default value. The default value is iipartNN.
with_clause: Specifies WITH clause options for partitioning. The with_clause for partitioning has the format WITH with-option, where with-option = LOCATION = (location). When specifying a LOCATION for the table, this location will only be used for PARTITIONS that are lacking a WITH LOCATION clause.
For more information about partitioning schemes, see Partitioned Tables section in Actian Vector documentation available at docs.actian.com.
Supported Output Modes
Actian Avalanche Multimode connector supports the Multimode output mode. For information about output modes, see Target Output Modes.
Data Types
Actian Avalanche Multimode connector supports the same data types supported by Actian Avalanche connector.