Forum Discussion
SQL CDC to Fabric
Hello J-Schreck,
The challenge with __$Start_LSN values appearing in binary format is expected behavior within SQL Server CDC. Since Fabric doesn’t handle this format directly, a practical approach is to convert the binary LSN values into a readable format (such as hexadecimal or timestamps) using SQL Server’s built-in functions, like CONVERT() or sys.fn_cdc_map_lsn_to_time()
sys.fn_cdc_map_lsn_to_time (Transact-SQL) - SQL Server | Microsoft Learn.For periodic CDC ingestion — given that real-time processing isn’t a requirement — Dataflows Gen2 or Data Factory pipelines are effective solutions within Fabric. These methods support scheduled data pulls and transformations.
To ensure you capture only new changes, I recommend tracking the last processed LSN in a Fabric table and using it as a reference point to fetch only incremental data on each load.
This approach should resolve the binary LSN issue and ensure smooth, repeatable CDC ingestion into Fabric.
I hope this could resolve you issue, if you need any further assistance, feel free to reach out.
If this post helps, then please give us Kudos and consider Accept it as a solution to help the other members find it more quickly.
Thank you for using Microsoft Community Forum.
but the start and end LSN values are still in binary format which makes it alsmost useless.
Jeff, yes these values are in binary format, but I am not sure why thats causing a concern for you.
If you need to copy data from a table that has CDC enabled, just point to the original table (not the CDC table), and the CopyJob UX should detect automatically that it has CDC enabled, and at runtime, we will automatically read from the backing CDC tables, you dont need to provide us LSN column or CDC table info.