Scan/cleanup are part of user workload (user's resources are used). Monitor space utilization closely and test your workload thoroughly before enabling CDC on databases in production. However, here's some more general guidance based on performance tests conducted on the TPCC workload:Ĭonsider increasing the number of vCores or shift to a higher database tier (for example, Hyperscale) to ensure the same performance level as before CDC was enabled on your Azure SQL Database. To provide more specific performance optimization guidance to customers, more details are needed on each customer's workload. Monitor resources such as CPU, memory and log throughput. Databases in a pool share resource among them (such as disk space), so enabling CDC on multiple databases runs the risk of reaching the max size of the elastic pool disk size. For databases in elastic pools, in addition to considering the number of tables that have CDC enabled, pay attention to the number of databases those tables belong to. Whether the database is single or pooled. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |