Forum Discussion
ISSUE: Fabric SQL database replication error to one-lake
Thankyou, ToddChitt and j_hoff for your responses.
Hi Max_agileDSS,We appreciate your inquiry submitted through the Microsoft Fabric Community Forum.
The backend team has resolved the issue, as shown in the screenshot below:
Please confirm whether you are still experiencing the problem. If you have any further queries, feel free to contact the Microsoft Fabric Community.
Thank you.
I've checked the note on the service status. However, this doesn’t seem to be exactly the same issue, but it might be a side effect… I’ll keep a close eye on it.
I’ll also ask my team to submit an issue to make sure they are working on it, since I’m still facing the problem.
I’ll let you know if I notice any changes.
Thanks !
I'm not sure if it was something I did or if the issue was resolved by Microsoft, but my Fabric SQL Database is replicating as intended again.
About 20 minutes ago, in the Fabric SQL Database I went to the Security tab -> Manage SQL Security, and added myself to all of the four built-in security roles. Did this change anything? I have no idea, as I am the owner of the SQL Database item. After doing this, I tried to "bump" the replication process by adding a column to my table that was showing a status of "RunningWithWarnings". I verified the new column showed up in the table and then dropped the column. I checked back a few minutes later and my table is now showing a status of "Running" in the Monitor Replication tab. I checked that the two columns I had tried to originally create had replicated to the SQL Analytics Endpoint and OneLake, and they had. I also created a new table in the dbo schema and it also replicated as intended.
I'm curious what you all find!
j_hoff This is a good lead and I think i've found a "dirty workaround"...
Here is the sequence that I did:
Created a SQL database.
Explicitly added the item owner to all four database roles.
Important: Even after adding the owner to the roles, I still got an error. So I paused and resumed the Fabric Capacity to make sure that i've forced db's to restart...
Waited until capacity is running, then execute EXEC sp_help_change_feed to check that the change feed/replication process is working ...
Added tables and data and the replication process ran successfully.
Although this seems to work, it remains a temporary solution that I can apply individually. It is not viable for my customer because there are users assigned to the current capacity and haves multiple SQL Databases. Nevertheless, it can be used as a desperate workaround. 🙂
Can you confirm that this sequence seems to work?!
Thanks! 🙂
That logic makes sense to me, I don't have a seperate capacity that I could try it on though.
In other news, it appears we've made it on to the support page 🙂