Forum Discussion
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 ...
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.
- The “Index was outside the bounds of the array” error affecting the same two tables across all three database instances suggests a schema-related issue rather than a data problem. This typically occurs when Fabric mirroring encounters unsupported data types, complex column structures, or special characters in column names that the parsing engine cannot handle properly.
- To resolve this, examine the schema of the failing tables compared to successful ones - look for unusual data types (like XML, geography, or deprecated types), special characters in column names, or complex constraints. You can also try testing individual columns by creating a subset table to isolate which specific columns are causing the parsing failure. Since the same tables fail consistently across different environments, the issue is likely in the table structure or metadata rather than the actual data content.