Skip to main content Skip to complementary content
Qlik Resources

Limitations and considerations

When using an Amazon RDS for SQL Server source endpoint in a Replicate task, the following imitations apply:

  • Amazon RDS for SQL Server moves the online logs to the backup location when the maximum allocated storage size is reached. This may sometimes occur before Replicate has read the logs, resulting in missing changes on the target.

    Therefore, in a system with a high volume of changes (or if you notice that some changes are not being captured), best practice is to increase the allocated storage size as described in How can I troubleshoot storage consumption in my Amazon RDS DB instance that is running SQL Server?

  • A Secondary SQL Server database is not supported as a source database.
  • The Amazon RDS for SQL Server Replication Publisher definitions for the database that was used in the task are not removed when you remove a task. an Amazon RDS for SQL Server system administrator must delete these definitions from Amazon RDS for SQL Server.
  • Sparse tables are not supported.
  • Replicating data from indexed views is not supported.
  • Renaming tables using sp_rename is not supported (e.g. sp_rename 'Sales.SalesRegion', 'SalesReg;)
  • Renaming columns using sp_rename is not supported (e.g. sp_rename 'Sales.Sales.Region', 'RegID', 'COLUMN';)
  • TRUNCATE events will not be captured.
  • Replication of computed columns is supported in Full Load replication tasks only. During CDC, INSERTs to computed columns will appear as NULL on the target and UPDATEs will be ignored.
  • Partition switching is not supported.
  • When using the WRITETEXT and UPDATETEXT utilities, Qlik Replicate does not capture events applied on the source database.

  • The following DML pattern is not supported:

    select <*> into <new_table> from <existing_table>

  • Column-level encryption is not supported.
  • Amazon RDS for SQL Server backup to multiple disks is not supported.
  • When inserting a value into SQL Server spatial data types (GEOGRAPHY and GEOMETRY), one can either ignore the SRID (Spatial Reference System Identifier) property - in which case the default SRID will be used (0 for GEOMETRY and 4326 for GEOGRAPHY) - or specify a different number. When replicating tables with spatial data types, Qlik Replicate replaces the SRID that was inserted by user with the default SRID.
  • Replicating GEOGRAPHY and GEOMETRY data types is only supported in limited LOB mode.
  • Columnstore indexes are not supported.
  • Memory-optimized tables (using In-Memory OLTP) are not supported.
  • Temporal databases are not supported
  • Delayed durability is not supported
  • Table change tracking is not supported
  • Masked data will be created in the target without masking.

  • Replication from databases configured to use ADR (Accelerated Database Recovery) is not supported.

  • Capturing DDL and DML statements within a single transaction is not supported.

  • Replicating a table or schema with an apostrophe (') in its name is not supported.

  • UPDATEs to a Primary Key/Unique Index that affect multiple rows may cause conflicts when applying the changes to the target. This may occur, for example, if the UPDATEs are applied to the target as INSERT/DELETE operations rather than a single UPDATE operation. In such a scenario (where UPDATEs to a Primary Key/Unique Index affect multiple rows), working in Batch optimized apply Change Processing mode is not supported as it may result in the table being ignored. Working in Transactional Apply Change Processing mode however, may result in constraint violations. If this happens, you either need to reload the relevant table or locate the problematic records in the Apply exceptions Control Table and edit them manually in the target database. See also: Change Processing Tuning.

  • Changes applied to the database using DACPAC will not be captured.

  • System tables and views are not supported.

Non-supported Amazon RDS for SQL server security features

Tables that use the following Amazon RDS for SQL Server security features are not supported:

  • Always Encrypted
  • Row-Level Security

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – let us know how we can improve!

Leave your feedback here