Forum Discussion

cseajs's avatar
cseajs
New Member
1 year ago
Solved

Error mirroring tables on Prem SQL to Fabric

We have 3 different databases on prem that I am trying to mirror to Fabric.  Twenty of the tables sync with no issues but in all 3 instances there are 2 tables ( all the same tables) that are having ...
SQL database
  • v-sdhruv's avatar
    v-sdhruv
    1 year ago

    Hi cseajs ,

    The error suggests that the issue is likely related to how the data is being parsed—possibly due to malformed or inconsistent structure in the source files or tables  you can follow the checks suggested by mabdollahi .

    Additonally, you can
    1.Try loading the tables manually into OneLake and use the “Load to Table” option to see if the issue reproduces.
    2. Enable raw data preview in your pipeline to inspect malformed rows.

    Hope this helps!
    If the response has addressed your query, please accept it as a solution so other members can easily find it.
    Thank you.

mabdollahi's avatar
mabdollahi
Advocate IV
1 year ago

Hi cseajs ,
The issue is likely due to unsupported or mismatched data types in those two specific tables; especially in primary keys or indexed columns. Even though the data is different, the table structure might include types like geometery, hierarchyid, or datetime2(7) that Fabric doesn't support well. Double-check the schema and data types across all three databases for those tables, clean up any null-only columns, and try syncing again.

Regards,
Mehrdad Abdollahi