Update azure-sql-database-troubleshoot.md #1329
Conversation
added verbiage for Mirroring with terminal errors scenario: To ensure your compute resources are not impacted and to minimize impact on operational Azure SQL database, Mirroring will be disabled on any persistent/terminal error
|
@im-microsoft : Thanks for your contribution! The author(s) have been notified to review your proposed change. |
|
Learn Build status updates of commit 888d4c3: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
|
@WilliamDAssafMSFT Important: When the changes are ready for publication, adding a #label:"aq-pr-triaged" |
| @@ -25,6 +25,7 @@ For troubleshooting the automatically configured mirroring for Fabric SQL databa | |||
| | Workspace deleted | Mirroring stops automatically | If mirroring is still active on the Azure SQL Database, execute the following stored procedure on your Azure SQL Database: `exec sp_change_feed_disable_db;`. | | |||
| | Fabric trial capacity expired | Mirroring stops automatically | See [Fabric trial capacity expires](../../get-started/fabric-trial.md#the-trial-expires). | | |||
| | Fabric capacity exceeded | Mirroring will pause | Wait until the overload state is over or update your capacity. Learn more from [Actions you can take to recover from overload situations](../../enterprise/throttling.md#actions-you-can-take-to-recover-from-overload-situations). Mirroring will continue once the capacity is recovered. | | |||
| | Any other terminal errors | Mirroring will be disabled | To ensure your compute resources are not impacted and to minimize impact on operational Azure SQL database, Mirroring will be disabled on any persistent/terminal errors | | |||
There was a problem hiding this comment.
@im-microsoft can we elaborate what are "persistent/terminal" errors, and how to check if SQL publisher is disabled?
There was a problem hiding this comment.
@linda33wj, sure, some of the persistent/terminal errors are Fabric Workspaces got deleted with SQL Publishing still running, SQL Publishing unable to write to LZ due to capacity paused/exceeded etc. Way to check if SQL publisher is disabled is to execute this SQL query:
SELECT is_data_lake_replication_enabled from sys.databases
If returned value is 0, it indicates SQL publisher is disabled.
Also, users can run the public stored procedure below, which is documented in the troubleshooting section below:
EXEC sp_help_change_feed;
The key columns to look for here are the table_name and state. Any value besides 4 indicates a potential problem.
There was a problem hiding this comment.
Customers don't know what a terminal error is. Can we say "persistent resource errors"? @im-microsoft
There was a problem hiding this comment.
sure @WilliamDAssafMSFT, i was contemplating on the terminal error verbiage. "persistent resource errors" or "persistent errors" both work
|
Moving this to the private repo. |
added verbiage for Mirroring with terminal errors scenario: To ensure your compute resources are not impacted and to minimize impact on operational Azure SQL database, Mirroring will be disabled on any persistent/terminal error
@WilliamDAssafMSFT @anagha-todalbagi @sukanyamsft, please review the verbiage to call out behavior for Mirroring disablement on any persistent/terminal errors.
Thank you for contributing to Microsoft Fabric documentation
Fill out these items before submitting your pull request:
If you are working internally at Microsoft:
Provide a link to an Azure DevOps Boards work item that tracks this feature/update.
Who is your primary Skilling team contact? @mention them individually tag them and let them review the PR before signing off.
For internal Microsoft contributors, check off these quality control items as you go
1. Check the Acrolinx report: Make sure your Acrolinx Total score is above 80 minimum (higher is better) and with no spelling issues. Acrolinx ensures we are providing consistent terminology and using an appropriate voice and tone, and helps with localization.
2. Successful build with no warnings or suggestions: Review the build status to make sure all files are green (Succeeded).
3. Preview the pages:: Click each Preview URL link to view the rendered HTML pages on the review.learn.microsoft.com site to check the formatting and alignment of the page. Scan the page for overall formatting, and look at the parts you edited in detail.
4. Check the Table of Contents: If you are adding a new markdown file, make sure it is linked from the table of contents.
5. #sign-off to request PR review and merge: Once the pull request is finalized and ready to be merged, indicate so by typing
#sign-offin a new comment in the Pull Request. If you need to cancel that sign-off, type#hold-offinstead. Signing off means the document can be published at any time. Note, this is a formatting and standards review, not a technical review.Merge and publish
#sign-off, there is a separate PR Review team that will review the PR and describe any necessary feedback before merging.#sign-offagain. The PR Review team reviews and merges the pull request into the specified branch (usually the main branch or a release- branch).