Data Ship Source and Target Support

Data ship optimization is supported for following data source types.

Data Source Type

Data Ship Source Support

Data Ship Target Support

Performance Option

Notes

DB2 v10.5

Active

Active

Bulk Load using the LOAD utility

LUW

Greenplum 3.3

Active

Active

 

 

Greenplum 4.1

Active

Active

 

 

Greenplum 4.3

Active

Active

 

 

Microsoft SQL Server 2008

Active

Active

Bulk import/export using BCP

 

Microsoft SQL Server 2012

Active

Active

Bulk import/export using BCP

 

Microsoft SQL Server 2014

Active

Active

Bulk import/export using BCP

 

Microsoft SQL Server 2016

Active

Active

Bulk import/export using BCP

 

Microsoft SQL Server 2019

Active

Active

Bulk import/export using BCP

 

Netezza 6.0

Active

Active

external tables

 

Netezza 7.0

Active

Active

external tables

 

Oracle 11g

Active

Active

Database Links

To use an Oracle data source for data ship, the DBA must install the DBMS_XPLAN package in the database and create an area for temporary tables.

For this data source to participate in data ship, it must be specified as a data ship source. Participation as a data ship target is optional. If Oracle is both source and target, DB Link needs to be set up between the Oracle databases.

Oracle 12c

Active

Active

Database Links

 

Oracle 19c

Active

Active

Database Links

 

PostgreSQL 9.1

Active

Active

Database Links

 

PostgreSQL 9.2.3

Active

Active

Database Links

 

Sybase IQ 15

Active

Active

Location:

iAnywhere JDBC driver

For a Sybase IQ data source to participate in data ship, the QUERY_PLAN_TEXT_ACCESS database option must be set to ON.

For this data source to participate in data ship, it must be specified as a data ship source. Participation as a data ship target is optional.

Teradata 13.00

Active

Active

FastLoad/
FastExport

For this data source to participate in data ship, it must be specified as a data ship source. Participation as a data ship target is optional.

Teradata Fastload mode doesn't work correctly using the 14.10 JDBC driver when Teradata is the Target Data Source. To workaround this issue, use a leter version of the Teradata JDBC driver.

Teradata 13.10

Active

Active

FastLoad/
FastExport

Teradata 14.10

Active

Active

FastLoad/
FastExport

Teradata 15

Active

Active

FastLoad

Teradata 16.20

Active

Active

FastLoad

Vertica 5.0

Inactive

Inactive

 

Vertica 6.1

Active

Active

Bulk load utility

Export to another Vertica database