Fix technical inaccuracies in DBCC CHECKIDENT doc #1602
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
1. No rows due to `DELETE` statement behaves the same as if rows are present 1. No behavior difference between various versions of SQL Server (I have tested on SQL Server 2005, 2008 R2, 2012, 2017, and 2019 CTP 2.2) 1. Fixed typo in example C: "increment" was used instead of "identity"
Contributor
Contributor
Contributor
Author
|
I did not realize that there were merge conflicts. Those have now been resolved. |
Contributor
|
@uc-msft - can you take a look at these submitted changes? thanks. |
Contributor
|
Hi @srutzky , thank you so much for your contribution, and sorry for the long delay! Your corrections are accurate, thanks for noticing and improving it :) #sign-off |
Contributor
|
@MashaMSFT: I'm sorry - only the author of this article, @uc-msft, can sign off on your changes. But we do have an exception process - if you are on the Microsoft content or product team for this product area, you can ask the PR review team to review and merge it by sending mail to the techdocprs alias. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
7 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
DELETEstatement behaves the same as if rows are presentFor full details and example code as proof, please see:
How Does DBCC CHECKIDENT Really Work When Resetting the Identity Seed (RESEED)?
( https://sqlquantumleap.com/2019/01/31/how-does-dbcc-checkident-really-work-when-resetting-the-identity-seed-reseed/ )