Forum Discussion
SQL Server Mirroring - special characters
Copy Job cannot handle special characters (eg. /) in column names - does SQL server Mirroring have the same issue - the documentation states that special characters are managed - list a number - but / is not on the list - this question is for us to plan our approach to bringing SQL Databases to Fabric
Hi Magic_Mads,
Microsoft Fabric relies on Delta Lake and Parquet formats under the hood for storage and querying. These technologies, along with Fabric’s mirroring and Lakehouse architecture, impose restrictions on special characters in column names due to file system compatibility and query engine parsing rules.
column names with special characters may cause errors in mirroring, dataflows, and Spark operations. The / character, although sometimes accepted in SQL Server, can break schema inference and querying in Fabric.
Thanks,
Prashanth Are
MS Fabric community support
11 Replies
Hi Magic_Mads
Just curious to ask, Why you have to create mirroring of SQL Server table. Everything is in Microsoft Fabric. Fabric SQL / Fabric Data Warehouse / Semantic Model using Unified Approach.
Again SQL Server Mirroring or Azure SQL Mirroring???
Hi - I am going to do mirroring from a SQL Server 2019-database hosted on prem - all I need to know is if a / in a column name is handled or nor - if not - morroring is out of the question
To clerify - Fabric Mirror from SQL Server on-prem to Fabric Lakehouse
Some of the data from SQL Server on-premises is not migrated to Fabric Mirror because They are the concept of using Windows vs Linux Systems. Until now, Microsoft (Windows ) was using SQL Server on premises whereas Fabric SQL ( Mirror ) is using Linux Systems. so, Definitely there is some mismatch for example, Copy jobs in Linux ( Delta Lake ) are using decimal data as compare to money data in Windows ( SQL Server on premises).
SQL Server on premises
Hi - it is Fabric Mirroring (SQL Server on-prem) - not in any way related to Windows vs. Linux
Behind the scene, it is Windows vs Linux Systems. You can not see this but We can see this behind the scene.
Also, In Delta Lake ( Linux Systems ), We are using Schema Evolution/ Schema Enforcement whereas in old days ( 8 yrs before ), there was only schema enforcement in SQL Server on premises.
Hi Magic_Mads,
Microsoft Fabric relies on Delta Lake and Parquet formats under the hood for storage and querying. These technologies, along with Fabric’s mirroring and Lakehouse architecture, impose restrictions on special characters in column names due to file system compatibility and query engine parsing rules.
column names with special characters may cause errors in mirroring, dataflows, and Spark operations. The / character, although sometimes accepted in SQL Server, can break schema inference and querying in Fabric.
Thanks,
Prashanth Are
MS Fabric community support
Hi Magic_Mads,
We would like to follow up to see if the solution provided by the super user resolved your issue. Please let us know if you need any further assistance.
Thanks,Prashanth Are
MS Fabric community support
If our super user response resolved your issue, please mark it as "Accept as solution" and click "Yes" if you found it helpful.Hi Magic_Mads,
We would like to follow up to see if the solution provided by the super user resolved your issue. Please let us know if you need any further assistance.
Thanks,Prashanth Are
MS Fabric community support
If our super user response resolved your issue, please mark it as "Accept as solution" and click "Yes" if you found it helpful.May I ask if you have resolved this issue? If so, please mark the helpful reply and accept it as the solution. This will be helpful for other community members who have similar problems to solve it faster.
If we don’t hear back, we’ll go ahead and close this thread. For any further discussions or questions, please start a new thread in the Microsoft Fabric Community Forum we’ll be happy to assist.
Thank you for being part of the Microsoft Fabric Community.
