Forum Discussion
All tables data rows duplicated and Identity columns altered to plain columns in Fabric SQL Database
I have a Fabric SQL Database I created in Dec 2025.
I created several tables with INT IDENTITY (1, 1) columns. During Dec 2025 and most of Jan 2025, they worked correctly. When I added a row, the IDENTITY column would increment. When I did the "script create table" in both SSMS and the Fabric web interface it would show the IDENTITY column correctly in the generated column.
I checked on the data yestery, Feb 2026 and found all the tables have duplicate data. And all the columns that were INT IDENTITY (1, 1) are not plain INT columns. When I add a new row, what used to be the IDENTITY column stays as NULL. When I do the "script create table" in both SSMS and the Fabric web interface, the IDENTITY part from the column is now gone.
Is there some option I missed? Is there something I did not understand about IDENTITY in the Fabric SQL Database? How do I prevent this from happening again?
8 Replies
Wow, that's... interesting.
This clarification is very helpful, and than you for the suggestion. I'll look into that more.
Hello drew-sk,
I removed the comment you are referring to due to your input of it being incorrect.
Thank you,
Natalie H.
Community Manager
Hi mikeburek,
Could you please provide a bit more information:
- Is this workspace part of any CI/CD, Git integration, or Deployment Pipeline setup?
- Are there any pipelines, notebooks, or Dataflow Gen2 processes that create, drop, or overwrite these tables?
- Were the tables ever recreated via scripts or automated deployments?
This will help determine whether the behavior is related to deployment workflows or data ingestion processes.
Contact the customer support
Hello mikeburek, hope you are doing well. It's been a while since your reply, so we just wanted to know if you were able to solve your issue. If not, I suggest raising a Microsoft Support ticket would be the best course of action at this points. Please share all the required details regarding the issue and the steps you took so far to solve it, that would help them better understand the issue and solve it sooner.
You can create a Microsoft support ticket with the help of the link below:
https://learn.microsoft.com/en-us/power-bi/support/create-support-ticketHello mikeburek,
We are following up once again regarding your query. Could you please confirm if the issue has been resolved through the support ticket with Microsoft?
If the issue has been resolved, we kindly request you to share the resolution or key insights here to help others in the community.
Thank you.
Use withcolumns function to avoid duplicate and it don't affect on data tables.
