Forum Discussion
Issues with MirroredDatabaseTableExecutionLogs Showing Blank Columns in Eventhouse
Hi Folks
I’m currently working on mirroring a SQL Server (on-prem) database into Eventhouse, and I’ve noticed that in the
MirroredDatabaseTableExecutionLogs table, columns like Status, ErrorType, and ErrorMessage are coming through as blank.
Despite these columns being empty, I am facing issues during the mirroring process, which makes troubleshooting difficult.
The challenge is that a few database tables are failing to mirror, but the logs are not capturing their current status or any error details, making it hard to troubleshoot.
Has anyone experienced this behavior?
- Why might these fields remain empty even when issues occur?
- Are there additional logs or diagnostic steps I can use to identify the root cause?
- Could this be related to permissions, connectivity, or Eventhouse ingestion pipeline configuration?
Any guidance or best practices would be greatly appreciated!
3 Replies
Most mirroring issues are caused by column types that are not (yet) supported in OneLake.
Limitations of Fabric Mirrored Databases From SQL Server - Microsoft Fabric | Microsoft Learn
Hi SinghPartap779,
I would also take a moment to thank lbendlin , for actively participating in the community forum and for the solutions you’ve been sharing in the community forum. Your contributions make a real difference.
I wanted to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions.
Regards,
Community Support Team.Hi SinghPartap779,
I hope the above details help you fix the issue. If you still have any questions or need more help, feel free to reach out. We are always here to support you.
Regards,
Community Support Team.
