This time we’re going bigger than ever. Fabric, Power BI, SQL, AI and more. We're covering it all. You won't want to miss it.
Learn moreJoin the FabCon + SQLCon recap series. Up next: Power BI, Real-Time Intelligence, IQ and AI, and Data Factory take center stage. All sessions are available on-demand after the live show. Register now
I have setup an Azure SQL mirror in a workspace using a service principal and the fabric REST API.
When I view the mirror on the workspace and choose "Start replication" it then switches to running. However the tables never replicate. If I then choose to "Configure Replication" I get a permissions error as the connection is owned by the service principal.
If I run `EXEC sp_help_change_feed;` on the source database, I can see everything is at State 1 (pending) while a manually setup (not using the API) mirror on another workspace generates state 4 results.
There is the issue that we cannot see the connection or configure replication as its owned by the principal. I am not sure if we can set that as shared using the API? But the main issue is the tables are not replicating even though the mirror shows as running.
Has anyone seen these issues?
Solved! Go to Solution.
For anyone reading this in the future, when the mirror is created by the API, you need to set the SAMI permissions either by going to the mirror in the portal and choosing share or by using an API call. I had not done that.
For anyone reading this in the future, when the mirror is created by the API, you need to set the SAMI permissions either by going to the mirror in the portal and choosing share or by using an API call. I had not done that.
| User | Count |
|---|---|
| 42 | |
| 24 | |
| 13 | |
| 12 | |
| 12 |