Forum Discussion
Azure SQL DB bug in identifying the primary key for table?
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 the Id int as the 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 document).
Thank you in advance.
Hi jozseftuska, we can confirm that this is a bug and in your scenario the table should NOT be blocked for Mirroring as you have a supported data type as a PK with a UK constraint of Date field. We'll work to have this bug resolved soon. Thanks for bringing this to our attention!
3 Replies
- lbendlin
Super User
sure sounds like a design oversight. If you have a Pro license you can open a Pro ticket at https://admin.powerplatform.microsoft.com/newsupportticket/powerbi
Otherwise you can raise an issue at https://community.fabric.microsoft.com/t5/Issues/idb-p/Issues . 
idrismotiwalaMicrosoft Employee
Hi jozseftuska, we can confirm that this is a bug and in your scenario the table should NOT be blocked for Mirroring as you have a supported data type as a PK with a UK constraint of Date field. We'll work to have this bug resolved soon. Thanks for bringing this to our attention!
This is still an issue and preventing us from fully evaluating Fabric.
idrismotiwala any update on when the fix will be released?
