Check your eligibility for this 50% exam voucher offer and join us for free live learning sessions to get prepared for Exam DP-700.
Get StartedDon't miss out! 2025 Microsoft Fabric Community Conference, March 31 - April 2, Las Vegas, Nevada. Use code MSCUST for a $150 discount. Prices go up February 11th. Register now.
Hi.
We want to try Fabric with a mirrored MSSQL database, however we get this error for several tables: This table can't be mirrored to Fabric because the primary key column uses one of the following data types: computed types, user-defined types, geometry, geography, hierarchy ID, SQL variant, timestamp, datetime2(7), datetimeoffset(7) or time(7).
However it's not true, we have int Id as primary key. I think it's because we have another unique constraint apart from the ID that also contains a date field. Is it a bug that the PK is being identified incorrectly or is it a limitation that we can't have unique constraint for date? (I did not find in the documentation).
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,@jozseftuska .I am glad to help you.
I found the following documentation on the relevant restrictions
URL:
Limitations and Behaviors for Fabric Mirrored Databases From Azure SQL Database - Microsoft Fabric |...
According to the documentation, certain data types cannot be used for the primary key, including calculated type, user-defined type, geometry, geography, hierarchy ID, SQL variant, timestamp, datetime2(7), datetimeoffset(7), and time(7)
You mentioned that the primary key of your table is the Id column of type int, but if there are other unique constraints in the table that contain date fields, this may cause the Fabric to mistakenly assume that the primary key is using an unsupported data type when processing the data.
Please try the following actions:
Make a backup of the table data that is currently experiencing the problem to prevent data loss. Temporarily remove the unique constraint that contains the date field.
Try loading the modified mirror table into the fabric again to see if the same error still occurs, if the problem disappears then this may indeed be an unwritten constraint.
Check the precision of the data in your mirrored table to ensure that it meets the requirements of the Fabric. If the problem persists after testing and you are able to ensure that the format and precision of the relevant data types in the mirrored table meets the documentation, then you may need to provide more detailed information, which will help you find the problem quickly.
I hope my suggestions give you good ideas, if you have any more questions, please clarify in a follow-up reply.
Best Regards,
Carson Jian