Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update sql-server-deadlocks-guide.md #9776

Closed
wants to merge 1 commit into from

Conversation

OleksiiKovalov
Copy link
Contributor

@OleksiiKovalov OleksiiKovalov commented May 3, 2024

adding information about how to handle deadlock error using try/catch block (see https://learn.microsoft.com/en-us/previous-versions/sql/sql-server-2005/ms179296(v=sql.90)?redirectedfrom=MSDN#working-with-trycatch)

@microsoft-github-policy-service agree

@OleksiiKovalov
Copy link
Contributor Author

@microsoft-github-policy-service agree

Copy link
Contributor

@OleksiiKovalov : Thanks for your contribution! The author(s) have been notified to review your proposed change.

Copy link
Contributor

Learn Build status updates of commit 57612dc:

✅ Validation status: passed

File Status Preview URL Details
docs/relational-databases/sql-server-deadlocks-guide.md ✅Succeeded

For more details, please refer to the build report.

For any questions, please:

@Jak-MS
Copy link
Contributor

Jak-MS commented May 3, 2024

@WilliamDAssafMSFT

  • Can you review this PR?
  • IMPORTANT: When this content is ready to merge, you must add #sign-off in a comment or the approval may get overlooked.

#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 May 3, 2024
@rwestMSFT
Copy link
Contributor

We've had some time to look at this contribution, and it is currently under review by the product group.

@AnnaMHuff AnnaMHuff closed this Sep 16, 2024
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