Hi, I'm Ask INFA!
What would you like to know?
ASK INFAPreview
Please to access Bolo.

Table of Contents

Search

  1. Introducing Mass Ingestion
  2. Getting Started with Mass Ingestion
  3. Connectors and Connections
  4. Mass Ingestion Applications
  5. Mass Ingestion Databases
  6. Mass Ingestion Files
  7. Mass Ingestion Streaming
  8. Monitoring Mass Ingestion Jobs
  9. Asset Management
  10. Troubleshooting

Mass Ingestion

Mass Ingestion

Mass Ingestion Databases connectors

Mass Ingestion Databases
connectors

Before you begin defining connections for
database ingestion
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
Mass Ingestion Databases
requires to connect to a source or target that can be configured in a
database ingestion
task:
Source or target type
Connector
Use for
Amazon Redshift
Amazon Redshift V2
Targets in initial load, incremental load, and initial and incremental load operations
Amazon S3
Amazon S3 V2
Targets in initial load and incremental load operations
Databricks Delta
Databricks Delta
Targets in initial load, incremental load, and initial and incremental load operations
Db2 for i
Db2 for i Database Ingestion
Sources in initial load, incremental load, and initial and incremental load operations
Db2 for Linux, UNIX, and Windows
Db2 for LUW Database Ingestion
Sources in initial load operations
Db2 for z/OS
Db2 for zOS Database Ingestion
Sources in initial load and incremental load operations
Flat file
No connector required
Targets in initial load and incremental load operations.
Google BigQuery
Google BigQuery V2
Targets in initial load, incremental load, and initial and incremental load operations
Google Cloud Storage
Google Cloud Storage V2
Targets in initial load and incremental load operations
Kafka, including Apache Kafka, Confluent Kafka, Amazon Managed Streaming for Apache Kafka, and Kafka-enabled Azure Event Hubs
Kafka
Targets in incremental load operations
Microsoft Azure Data Lake Storage Gen2
Microsoft Azure Data Lake Storage Gen2
Targets in initial load and incremental load operations
Microsoft Azure SQL Database
Microsoft SQL Server
Sources in initial load operations
Microsoft Azure Synapse Analytics
1
Microsoft Azure Synapse Analytics Database Ingestion
Targets in initial load, incremental load, and initial and incremental load operations
Microsoft SQL Server
Microsoft SQL Server
Sources in initial load, incremental load, and initial and incremental load operations
MongoDB
MongoDB Mass Ingestion
Sources in initial load and incremental load operations
MySQL, including RDS for MySQL
MySQL
Sources in initial load operations
Netezza
Netezza
Sources in initial load operations
Oracle, including RDS for Oracle
Oracle Database Ingestion
Sources in initial load, incremental load, and initial and incremental load operations
Targets in initial load, incremental load, and initial and incremental load operations
PostgreSQL, including RDS for PostgreSQL and Amazon Aurora PostgreSQL
PostgreSQL
Sources in initial load and incremental load operations
SAP HANA
SAP HANA Database Ingestion
Sources in initial load and incremental load operations
Snowflake
Snowflake Data Cloud Connector
Targets in initial load, incremental load, and initial and incremental load operations
Teradata Data Warehouse Appliance
Teradata
Sources in initial load operations
  1. For this target type, Mass Ingestion Databases uses Microsoft Azure SQL Data Lake Storage Gen2 to store staging files. Ensure that you have Microsoft Azure SQL Data Lake Storage Gen2 installed.

0 COMMENTS

We’d like to hear from you!