Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

In this article

...

Field Name

Field Type

Description

Label*

String

Specify a unique label for the account.

Default Value: N/A
Example: Generic Database Account

Account properties*The information required to create a connection to the database.

JDBC JARs

Use this field set to define JDBC Drivers. This field set consists of the JDBC Driver field.

JDBC Driver*String

Specify the JDBC driver to use. Click the Upload icon to upload the JDBC driver that you want. Click Add  to add a row for specifying a JDBC driver. Specify each driver in a separate row.

Note
  • Type 3 and Type 4 JDBC drivers are only supported. Type 4 JDBC driver is recommended. For more information on JDBC driver versions and downloads, see https://www.ibm.com/support/pages/db2-jdbc-driver-versions-and-downloads
  • You can upload the JDBC drivers through Designer or Manager and it is stored on a per project basis. That is, only users with access to that project can view the uploaded JDBC drivers. To provide access to all users of your org, place the driver in the /shared project.
  • We recommend you to use the db2jcc.jar driver for DB2 with your JDBC account. The DB2 version 11.5 supports only JDBC 4.0 Driver (db2jcc4.jar) and 11.1 version supports JDBC 3.0 driver (db2jcc.jar) and JDBC 4.0 Driver (db2jcc4.jar).

Default Value: N/A
Examplevertica-jdk5-6.1.2-0.jar

JDBC Driver Class*

String

Specify the JDBC Driver class name to use.

Default Value: [None]
Examplecom.vertica.jdbc.Driver

JDBC URL

String

Specify the JDBC URL to use.

Default Value: [None]
Example: jdbc:vertica://Snaplogic.com/database

UsernameString

Specify the database username to use.

Default Value: N/A
ExampleSnapuser

PasswordString

Specify the database password to use.

Default Value: N/A
Example: k*#!@09

Database nameString

Choose a database to which the account must be connected. The available options are:

  • Auto detect
  • PostgreSQL
  • Redshift
  • MySQL
  • Oracle
  • SQL Server 2012
  • SQL Server 2008
  • SAPHana
  • Apache Hive
  • DB2
  • SQLMX
  • Apache Derby
  • Spark SQL

If you use PostgreSQL JDBC driver to connect to Redshift database, the Auto detect option automatically detects the PostgreSQL database instead of Redshift. The behavior of the JDBC Snaps is optimized for the selected database.

Default Value: Auto detect
Example: Oracle

Test QueryString

Activates on selecting on selecting Auto detect for Database name.

Specify a custom query to validate the database connection.

Note
  • The Test Query must be effective as this executes multiple times during the lifecycle of a connection. The efficiency of a Test Query directly affects the efficiency of the Pipeline execution. All databases do not support all test queries. Hence, use a query that supports your database.
  • Select 1 test query is supported only in H2, MySQL, PostgreSQL, and SQLite databases.

Default Value: N/A
Example: Select 1

Advanced properties*
Min pool size*Integer

Specify a minimum number of idle connections a pool will maintain at a time.

Default Value: 0
Example: 0

Note

If the size is set to non-zero, JCC restart is needed when the database account expires.


Max pool size*IntegerSpecify a maximum number of idle connections a pool will maintain at a time.

Default Value: 15
Example: 10
Max idle time*IntegerSpecify the number of seconds a connection will exist in the pool before being destroyed.

Default Value: 60 
Example: 300
Checkout timeout*IntegerSpecify the number of milliseconds to wait for a connection to be available in the pool. A timeout of zero makes the Snap wait infinitely.  After a certain time, an exception is thrown and the Pipeline fails.

Default Value: 10000
Example:10000
Url propertiesUse this field set to define URL properties to use in the JDBC URL.

Url property nameString

Specify the name for the URL property.

Default Value: N/A
Example: maxAllowedPacket

Url property valueString

Specify a value for the property name.

Default Value: N/A
Example1000

Auto commitCheckbox

Select this checkbox to commit a batch immediately after the batch executes. So, only the current executing batch will be rolled back if the Snap fails.
If you deselect, then a transaction is started for the Snap run and committed upon run success. The transaction is rolled back if the Snap fails.

Default Value
: Selected

Fetch size*IntegerSpecify the number of records to retrieve from the DB at a time.

Default Value: 100
Example: 100
Batch size*

Integer

Specify the number of query statements to execute at a time. SELECT queries are not batched.

  • If the Batch Size is one, the query is executed as-is, that is the Snap skips the batch (non-batch execution).

  • If the Batch Size is greater than one, the Snap performs the regular batch execution.

Default Value50
Example10

...