-
Notifications
You must be signed in to change notification settings - Fork 1k
Update sql-performance.md #3846
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
Conversation
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!
@FranciscoNabas : Thanks for your contribution! The author(s) have been notified to review your proposed change.
@FranciscoNabas : Thanks for your contribution! The author(s) have been notified to review your proposed change.
|
Learn Build status updates of commit f0bc9a9 : ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
Banreet
commented
May 4, 2023
#sign-off
@FranciscoNabas : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change.
MandiOhlinger
commented
Dec 10, 2025
@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.
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:
image
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!