No, you do not need to re-enable load balancing after customizing the weight of the cloud database SQL Server. Load balancing typically operates based on predefined rules or configurations, and adjusting the weight of backend instances (such as SQL Server nodes) is a dynamic adjustment within the existing load balancing setup. The load balancer will automatically apply the new weights to distribute traffic accordingly without requiring a restart or re-enablement of the service.
For example, if you have a load balancer distributing traffic across three SQL Server instances with weights set to 10, 20, and 30, and you later change the weights to 15, 25, and 35, the load balancer will immediately use the updated weights for traffic distribution. No additional steps are needed unless the load balancer itself requires a configuration reload (which is rare in modern systems).
In the context of cloud services, if you're using a managed database service with built-in load balancing (such as Tencent Cloud's TencentDB for SQL Server), the platform handles weight adjustments internally. You can modify the weights through the console or API, and the system will apply the changes dynamically. Tencent Cloud's load balancing solutions, like CLB (Cloud Load Balancer), are designed to work seamlessly with such configurations, ensuring high availability and optimal performance without manual intervention.