Skip to content

Conversation

@kendra-little
Copy link
Contributor

Please document that the catalog corruption can cause stack dumps and crashes of the SQL Server service. This has been verified by Microsoft Support, see case TrackingID #2504240010002403

Please document that the catalog corruption can cause stack dumps and crashes of the SQL Server service. This has been verified by Microsoft Support, see case TrackingID #2504240010002403
@prmerger-automator
Copy link
Contributor

@kendra-little : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change.

@learn-build-service-prod
Copy link
Contributor

Learn Build status updates of commit 0d5dd9b:

✅ Validation status: passed

File Status Preview URL Details
azure-sql/managed-instance/doc-changes-updates-known-issues.md ✅Succeeded

For more details, please refer to the build report.

For any questions, please:

@v-dirichards
Copy link
Contributor

@MashaMSFT

Can you review the proposed changes?

Important: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

@prmerger-automator prmerger-automator bot added the aq-pr-triaged tracking label for the PR review team label Jun 3, 2025
@rwestMSFT rwestMSFT assigned rwestMSFT and unassigned MashaMSFT Jun 3, 2025
@rwestMSFT
Copy link
Contributor

Checking with product group.

@kendra-little
Copy link
Contributor Author

I think that this issue actually does not cause service crashes (evidence points to a misdiagnosis by Microsoft support), so closing this PR. Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants