Limitations and considerations

Mirrored Database limitations and considerations

• Replicate produces data files to the Fabric landing zone. As processing in the landing zone may take time to complete, Replicate considers the records as processed (that is, loaded to the target) as soon as the files arrive in the landing zone. Additionally, there is no indication of whether the last file was processed or not. This means that there might be cases where a record was not loaded to the target (due to a data error, for example), but the Replicate monitoring counter will show that the record as having been loaded to the target.
• Tasks must run in Transactional apply mode, even though there are no transactions on the target. In other words, Batch optimized apply mode is not supported.
• TRUNCATE is not supported
  • The following task settings related to truncation are not supported:
    • Full Load Settings > If target table already exists: TRUNCATE before loading
    • Change Processing > Store Changes Settings > If change table exists : Delete old changes
  • During CDC, truncate from source is not supported
• UPDATE and DELETE operations are supported with tables that have a primary key only
• The source endpoint must provide full records for UPDATE operations. For example, when using Oracle as a source, full supplemental logging must be enabled.
• The only supported DDL changes are CREATE TABLE, ADD COLUMN, and DROP TABLE