Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hi
We have worked through the Qlik Replicat documentation. Fortunately, we didn't get there clear answers does Qlick Replication supports our planned setup (a problem that we like to resolve). Hope somebody on the product team or community is able to give an answer or advice.
Our application runs on an On-Prem SQL Server High Availability (Distribute Availability Group ( 3 x AG)). We like to read changes from Backup Logs Only on a single Availability Group.
Does Qlik Replicate support that scenario or what will be other recommendations on how is best to catch change with minimal impact on production? Does MS SQL Server CDC should be enabled or not?
Thanks in advance
You can read from backup files only, there are some internal settings you may need to adjust in the connection settings. Replicate Support can provide specifics. Native SQL CDC does NOT need to be enabled in any scenario for Replicate to to function.
From my personal perspective and four+ years using Replicate, I'd advise using a remote distributor and redirecting your AOG listener to it. This technique is documented well online. We have found very little impact on our production systems (300+ tables being replicated) using both Replicate capture data changes and storing data changes (Replicate CDC) using the technique of reading the online logs first, then backups second. We have very active online systems that we are capturing changes from and have experienced little or no impact using that method versus reading backup logs only.
Hi @rloppe ,
Adding to @PGN. If you decide to read from only backup logs then choose the direct reader option so Replicate directly reads from .trn which will provide the best performance compared with .trn read by SQL server.
Thanks,
Swathi
You can read from backup files only, there are some internal settings you may need to adjust in the connection settings. Replicate Support can provide specifics. Native SQL CDC does NOT need to be enabled in any scenario for Replicate to to function.
From my personal perspective and four+ years using Replicate, I'd advise using a remote distributor and redirecting your AOG listener to it. This technique is documented well online. We have found very little impact on our production systems (300+ tables being replicated) using both Replicate capture data changes and storing data changes (Replicate CDC) using the technique of reading the online logs first, then backups second. We have very active online systems that we are capturing changes from and have experienced little or no impact using that method versus reading backup logs only.
Hi @rloppe ,
Adding to @PGN. If you decide to read from only backup logs then choose the direct reader option so Replicate directly reads from .trn which will provide the best performance compared with .trn read by SQL server.
Thanks,
Swathi