Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
ALERT: QlikView server communication interruptions following Microsoft Windows Domain Controller security updates

Qlik Replicate with Microsoft Azure SQL Database Target: DATETIME PK Causes "0 Rows Affected"

No ratings
cancel
Showing results for 
Search instead for 
Did you mean: 
DesmondWOO
Support
Support

Qlik Replicate with Microsoft Azure SQL Database Target: DATETIME PK Causes "0 Rows Affected"

Last Update:

Mar 19, 2026 2:26:28 AM

Updated By:

Sonja_Bauernfeind

Created date:

Mar 19, 2026 2:26:28 AM

In homogeneous replication, when operating in Transactional Apply mode or in Batch Optimized Apply mode that falls back to One-by-One apply, a "0 rows affected" error occurs if a DATETIME column is part of the primary key on the target.

 

Resolution

Upgrade your version of Qlik Replicate.

Fix Versions:

  • Qlik Replicate v2025.5.0.583 SP04
  • Qlik Replicate v2025.11.0.285 SP02

 

Cause

In Transactional Apply mode or One-by-One mode, Qlik Replicate generated a WHERE clause that cast the column as DATETIME2(3). Since the precision of DATETIME and DATETIME2(3) differs, the mismatch prevented the record from being found, resulting in the “0 rows affected” message.

 

Investigation IDs

  • RECOB-10762
  • Case: 412967

 

 

Environment

  • Qlik Replicate
Labels (1)
Version history
Last update:
‎2026-03-19 02:26 AM
Updated by: