We had a few incidents here replication either stopped completely after a data centre crash or had irrecoverable errors. In all cases we had to fully restore database or delete and start again.
We need the following features to help support replication and have smoother recovery from failures
- Start replication on GUI and API
- Stop replication on GUI and by API (The existing SQLDB API works here for Fabric)
- Query replication state on GUI and by API
- Resync either one table or all tables on GUI or by API.
These features would allow for recovery from issues without having to do full restores and reduce customers down time.
2 Comments
- fbcideas_migusrNew MemberStatus added:Under Review
- idrismotiwalaMicrosoft EmployeeStatus changed:Under ReviewtoPlanned
bob_duffy we do plan to enable Start & Stop replication in the next release cycle. Ability to configure select/specific custom tables is backlogged and be enabled at a later phase.
Recent ideas
Disable auto-restore previous session's tabs in new Fabric sessions
Description: Since a recent update, starting a new Fabric session — for example by opening Fabric in a new browser tab — automatically reopens all the item tabs that were left open from a previous s...MathieuVr34 minutes agoFrequent VisitorNew56Views5likes1CommentExported PDF from PowerBI to not have any indents/borders
Currently, using the "Export to PDF" option in PowerBI results in two consistently buggy results: A white border/indent is generated, increasing the size of the page from 8.5x11 to 9x11.5 Sometime...EliShalev3 hours agoNew MemberNew8Views0likes0CommentsAdding a Container for Logical Grouping of Activities in Data Pipelines
Dear Team, I would like to propose a feature enhancement for Data Pipelines in Microsoft Fabric that allows the logical grouping of activities into a container. This container would serve to: Im...lukas_karlovsky4 hours agoNew MemberPlanned875Views15likes5Comments