Replicate offers two methods to capture changes from a Microsoft SQL Server source database: one that reads from the transaction log (TLOG), and another that leverages Microsoft CDC (Change Data Capture). However, due to limitations in Microsoft SQL Server itself—not Replicate—neither method can capture changes from tables that use Columnstore Indexes. This limitation is documented in Microsoft's official documentation: Columnstore indexes can't be combined with the following features.
As workarounds, you may consider the following alternatives:
Using a View on the affected table – This enables Full Load ONLY replication, which can be scheduled at regular intervals (e.g., every 30 minutes) to mimic change capture.
Regards,
John.
Help users find answers! Do not forget to mark a solution that worked for you! If already marked, give it a thumbs up!
Thank you for providing the alternate solutions. I will definitely give them a try.
Additionally, could we consider presenting this limitation to the R&D Team as a potential area for ideation? This might help us find a faster solution.
Tickets submitted in the Ideation area are reviewed by our Product Management team. Other users can vote on these ideas, which helps influence prioritization and increases the likelihood of adoption.
According to current guidelines, Feature Requests should be submitted directly by users, rather than by the support team.
Please feel free to reach out if you need any further assistance!
Regards,
John.
Help users find answers! Do not forget to mark a solution that worked for you! If already marked, give it a thumbs up!
