Connectors and Connections > Data Ingestion and Replication connectors > Database Ingestion and Replication connectors
  

Database Ingestion and Replication connectors

Before you begin defining connections for database ingestion and replication tasks, verify that the connectors for your source and target types are available in Informatica Intelligent Cloud Services.
The following table lists the connectors that Database Ingestion and Replication requires to connect to a source or target that can be configured in a database ingestion and replication task:
Source or target type
Connector
Use for
Amazon Redshift
Amazon Redshift V2
Targets, all load types1
Amazon S3
Amazon S3 V2
Targets, all load types
Databricks
Databricks
Targets, all load types
Db2 for i
Db2 for i Database Ingestion
Sources, all load types
Db2 for Linux, UNIX, and Windows
Db2 for LUW Database Ingestion
Sources, initial loads, and incremental loads and combined loads that use Query-based CDC
Db2 for z/OS
Db2 for zOS Database Ingestion
Sources, all load types
Flat file
No connector required
Targets, initial load jobs
Google BigQuery
Google BigQuery V2
Targets, all load types
Google Cloud Storage
Google Cloud Storage V2
Targets, all load types
Kafka, including Apache Kafka, Confluent Kafka, Amazon Managed Streaming for Apache Kafka, and Kafka-enabled Azure Event Hubs
Kafka
Targets, incremental load type
Microsoft Azure Data Lake Storage Gen2
Microsoft Azure Data Lake Storage Gen2
Targets, all load types
Microsoft SQL Server, including on-premises SQL Server, RDS for SQL Server, Azure SQL Database, and Azure SQL Managed Instance
SQL Server
Sources, all load types. For Azure SQL Database sources, you must use the Query-based or CDC Tables capture method for incremental load and combined load jobs.
Targets, all load types
Microsoft Azure Synapse Analytics2
Microsoft Azure Synapse Analytics Database Ingestion
Targets, all load types
Microsoft Fabric OneLake
Microsoft Fabric OneLake
Targets, all load types
MongoDB
MongoDB Mass Ingestion
Sources, initial load and incremental load types
MySQL, including RDS for MySQL
MySQL
Sources, initial load and incremental load types. RDS for MySQL in initial load jobs only.
Netezza
Netezza
Sources, initial load type
Oracle, including RDS for Oracle
Oracle Database Ingestion
Sources, all load types
Targets, all load types
Oracle Cloud Infrastructure (OCI) Object Storage
Oracle Cloud Object Storage
Targets, all load types
PostgreSQL, including on-premises PostgreSQL, Amazon Aurora PostgreSQL, Azure Database for PostgreSQL - Flexible Server, RDS for PostgreSQL, and Cloud SQL for PostgreSQL
PostgreSQL
Sources, all load types
Targets (Amazon Aurora PostgreSQL targets only), all load types
SAP HANA, including on-premises SAP HANA and SAP HANA Cloud
SAP HANA Database Ingestion
Sources, initial load and incremental load types
Snowflake
Snowflake Data Cloud
Targets, all load types
Teradata Data Warehouse Appliance
Teradata
Sources, initial load type
1. Load types are initial load, incremental load, and combined initial and incremental load.
2. For the Microsoft Azure Synapse Analytics target type, Database Ingestion and Replication uses Microsoft Azure SQL Data Lake Storage Gen2 to store staging files. Ensure that you have Microsoft Azure SQL Data Lake Storage Gen2 installed.

Mock connectors

Database Ingestion and Replication supports mock, or sample, connections for some of the sources and targets. Use mock connections to learn how to create database ingestion and replication initial load tasks without creating real connections to the database.
A mock connector does not connect to a real database. Instead, a source mock connector uses flat files with sample data. A target mock connector reports the information about processed source data to Database Ingestion and Replication user interface, but it does not write any data to the target.
The sample connections appear in the source and target connection lists in Database Ingestion and Replication if you have the MockConnector license.
The following table lists mock connections that you can use for Database Ingestion and Replication sources and targets:
Connection name
Source or Target
Sample Oracle Connection
Source
Sample SQL Server Connection
Source
Sample S3 Connection
Target
Sample ADLS Gen2 Connection
Target
Note: You must use sample connections for both the source and target databases. You cannot use a sample connection for only one of them, for example, for the source but not for the target.

Source data

The source data for sample connections is stored in CVS files in the following directory:
Secure_Agent_installation/downloads/package-MockConnector.version/package/sampleData/source/database_type/
Each file represents a single table. A mock table name matches the file name. The first line in a file determines column headers, and the subsequent lines contain row data.