Join us for an expert-led overview of the tools and concepts you'll need to pass exam PL-300. The first session starts on June 11th. See you there!
Get registeredJoin us at FabCon Vienna from September 15-18, 2025, for the ultimate Fabric, Power BI, SQL, and AI community-led learning event. Save €200 with code FABCOMM. Get registered
Hello Everyone,
We are streaming data from Azure PostgreSQL CDC to Eventhouse and encountering issues with missing or duplicate records, likely due to inconsistencies in how CDC events are captured, processed, or committed into Fabric OneLake.
The input from PostgreSQL into Event Stream appears correct, but when the data is stored in KQL, we are seeing either fewer or more records than expected.
Has anyone used Azure PostgreSQL as a source connector with KQL as the destination? We are unable to use Lakehouse as the destination due to a conversion error, which the Microsoft PG team is currently investigating.
Any insights would be greatly appreciated.
Thank you!
Solved! Go to Solution.
Hi @PrachiJain_2025 ,
I tested it myself according to the steps in this document, but I didn't find any problems.
Add PostgreSQL Database CDC source to an eventstream - Microsoft Fabric | Microsoft Learn
However, the amount of data I tested was small. How big is your data? Are there multiple data tables involved?
You can try to modify some restriction policies in the KQL database using these commands and then re-import to see if the problem still exists.
Request limits policy - Kusto | Microsoft Learn
Also, I saw you mentioned:
the Microsoft PG team is currently investigating
If you find a solution in your feedback, please remember to reply the problem and solution below so that other users can find the solution faster. Thank you!
Best Regards,
Dino Tao
Hi @PrachiJain_2025 ,
I tested it myself according to the steps in this document, but I didn't find any problems.
Add PostgreSQL Database CDC source to an eventstream - Microsoft Fabric | Microsoft Learn
However, the amount of data I tested was small. How big is your data? Are there multiple data tables involved?
You can try to modify some restriction policies in the KQL database using these commands and then re-import to see if the problem still exists.
Request limits policy - Kusto | Microsoft Learn
Also, I saw you mentioned:
the Microsoft PG team is currently investigating
If you find a solution in your feedback, please remember to reply the problem and solution below so that other users can find the solution faster. Thank you!
Best Regards,
Dino Tao