Database ingestion and replication jobs that have a SQL Server source with IMAGE columns that contain nulls and a SQL Server target might fail if you create a custom data-type mapping that maps the IMAGE data type to the VARBINARY data type. In the case, the following error issued:

(October 2024)

A database ingestion and replication incremental load job that has a SQL Server source and contains a table that is not capturing a complete column set, such as excluded LOB or computed columns, might result in corrupted data when performing an Update operation. The job might continue to run without failing.

(October 2024)

A database ingestion and replication incremental load or combined load job that has a SQL Server target might not roll back the target transaction if the transaction fails to commit a recovery checkpoint.

(October 2024)

Database ingestion and replication initial load jobs that have a SQL Server target and process a large amount of data fail if the target connection drops. The jobs cannot retry the target connection. In this case, you have to restart the jobs from the earliest available position in the log, which is inefficient.

(August 2024)

Database ingestion and replication combined load jobs that have a SQL Server source and SQL Server target fail to clean up temporary data files after the initial load phase completes and the data has been loaded to the target. These data files can consume gigabytes of storage unnecessarily.

(August 2024)

If you configure a SQL Server connection to use the

Active Directory Password

authentication mode and then use that connection for database ingestion and replication incremental load jobs that connect to an Azure SQL Database source, the jobs use another authentication mode, which causes the connection to fail.

(August 2024)

Database ingestion and replication jobs that have a SQL Server source and SQL Server target might fail with the following error when processing large queries to the database:

The problem persists even after the job is undeployed, the tables on the target are dropped, and the job is deployed again.

(July 2024)

Database ingestion and replication

initial load jobs that use the Informatica-supplied Progress DataDirect JDBC driver for SQL Server to connect to a SQL Server source fail.

Workaround: Download the Microsoft JDBC Driver for SQL Server.

(September 2022)

Database ingestion and replication

incremental load or combined initial and incremental load jobs that have a SQL Server source with binary, decimal, or datetimeoffset columns and an Oracle target fail if a DML update operation is followed by an insert.

Workaround: None.

(May 2022)