Update sql-performance.md #3846
Open
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
The default retention period for change tracking on MS SQL Server is 2 days, but for the configuration manager, it should always be 5 days. The places where I got this info from: - When installing a site server, the database auto cleanup retention period is 5 days. - When looking the code for the stored procedure 'spDiagChangeTracking', while gathering change tracking information we can see a comment saying that for SCCM it should always be 5 days (screen shot will be included in the PR). - While troubleshooting a change tracking issue, I've set the retention for two days, and the auto cleanup couldn't keep up. I understand that while troubleshooting performance issues, cleaning the change tracking information up to 2 days can improve performance, however this can be misleading, since this query will always return 'there is change tracking backlog, please contact Microsoft support'. Cleaning more change tracking than default can also mask the real cause for performance issues. Thank you!
Contributor
|
@FranciscoNabas : Thanks for your contribution! The author(s) have been notified to review your proposed change. |
Contributor
|
@FranciscoNabas : Thanks for your contribution! The author(s) have been notified to review your proposed change. |
Contributor
|
Learn Build status updates of commit f0bc9a9: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
Banreet
approved these changes
May 4, 2023
Contributor
|
#sign-off |
JohanFreelancer9
approved these changes
May 4, 2023
prmerger-automator
bot
requested review from
Banreet,
aczechowski and
mestew
Contributor
|
@FranciscoNabas : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. |
Contributor
|
@FranciscoNabas Hi Francisco - This PR has a merge conflict. If it's still needed, can you create a new pull request? We want to make sure you get credit. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 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.
The default retention period for change tracking on MS SQL Server is 2 days, but for the configuration manager, it should always be 5 days. The places where I got this info from:
I understand that while troubleshooting performance issues, cleaning the change tracking information up to 2 days can improve performance, however this can be misleading, since this query will always return 'there is change tracking backlog, please contact Microsoft support'. Cleaning more change tracking than default can also mask the real cause for performance issues.
Thank you!