Update sql-performance.md

[FranciscoNabas]

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.

• 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!

[prmerger-automator[bot]]

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

[prmerger-automator[bot]]

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

[learn-build-service-prod[bot]]

Learn Build status updates of commit f0bc9a9:

:white_check_mark: Validation status: passed

File	Status	Preview URL	Details
memdocs/configmgr/core/servers/manage/replication/sql-performance.md	:white_check_mark:Succeeded

For more details, please refer to the build report.

For any questions, please:

• Try searching the learn.microsoft.com contributor guides
• Post your question in the Learn support channel

[Banreet]

#sign-off

[prmerger-automator[bot]]

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