Merge pull request #21617 from MicrosoftDocs/MikeRayMSFT-patch-1

Change to site relative links

Author: PRMerger3

docs/relational-databases/track-changes/about-change-data-capture-sql-server.md

@@ -54,11 +54,11 @@ To provide more specific performance optimization guidance to customers, more de
 
 - Monitor space utilization closely and test your workload thoroughly before enabling CDC on databases in production.
 
-- Monitor log generation rate. To learn more [here](https://docs.microsoft.com/azure/azure-sql/database/resource-limits-logical-server#resource-consumption-by-user-workloads-and-internal-processes). 
+- Monitor log generation rate. To learn more [here](/azure/azure-sql/database/resource-limits-logical-server#resource-consumption-by-user-workloads-and-internal-processes). 
 
 - Scan/cleanup are part of user workload (user’s resources are used). Performance impact can be substantial since entire rows are added to change tables and for updates operations pre-image is also included.  
 
-- Elastic Pools - Number of CDC-enabled databases should not exceed the number of vCores of the pool, in order to avoid latency increase. Learn more about resource management in dense Elastic Pools [here](https://docs.microsoft.com/azure/azure-sql/database/elastic-pool-resource-management). 
+- Elastic Pools - Number of CDC-enabled databases should not exceed the number of vCores of the pool, in order to avoid latency increase. Learn more about resource management in dense Elastic Pools [here](/azure/azure-sql/database/elastic-pool-resource-management). 
 
 - Cleanup – based on the customer's workload, it may be advised to keep the retention period smaller than the default of 3 days, to ensure that the cleanup catches up with all changes in change table. In general, it is good to keep the retention low and track the database size.