Use Transaction Log Backup Files with AWS RDS for Microsoft SQL Server (MS SQL) for Qlik Replicate
Currently, Qlik Replicate has to use MS CDC with AWS RDS for Microsoft SQL Server (MS SQL) as as Source Endpoint. This is because AWS automatically performs Transaction Log backups every 5 minutes. If Qlik Replicate doesn't pick up all the transactions within these 5 minutes, the online T-Log gets truncated causing replication task to crash.
It would be great if Qlik Replicate started utilizing RDS MSSQL transaction log backups to catch up when if falls behind. Just like it does with conventional MS SQL Server as a Source Endpoint. This would eliminate the need to use MS CDC as it creates additional overhead to the source instance.
Amazon Relational Database Service (Amazon RDS) for SQL Server now supports access to transaction log backups. With this feature, customers can gain access to transaction log backups that are generated on the Amazon RDS SQL Server instance and copied to a customer S3 bucket. Subsequently, customers can restore single databases on that DB instance to a specific point-in-time using these transaction logs backups. Customers may also use the transaction log backups to audit, replicate, or process the log data. To get started, visit the Amazon RDS User Guide.
NOTE: Upon clicking this link 2 tabs may open - please feel free to close the one with a login page. If you only see 1 tab with the login page, please try clicking this link first: Authenticate me! then try the link above again. Ensure pop-up blocker is off.
