Overview
Last updated: 2024-01-18 17:20:34
TencentDB for SQL Server supports flexible scaling that allows you to quickly adjust instance architecture, version, and specification in the console. You can do so at any time (at the start, during rapid development, or during peak/off-peak hours), so you can get the most out of your resources and reduce unnecessary costs in real time.
Prerequisites
You can adjust the configuration of a TencentDB for SQL Server instance and its associated instances only when they are in running status and are not executing any tasks.
Adjustment item
Adjustment Item | Description |
Architecture | a. Single-node (formerly Basic Edition) instances cannot be upgraded to two-node (formerly High Availability/Cluster Edition) instances. If needed, you can purchase new two-node instances and migrate the data with DTS. |
Version | a. Both single-node (formerly Basic Edition) and two-node (formerly High Availability/Cluster Edition) instances support version upgrade. b. To upgrade the version of a two-node (formerly High Availability/Cluster Edition) instance associated with a read-only instance, disassociate the read-only instance first before upgrading or submit a ticket for assistance. |
Instance specification | a. All instance types support specification upgrade and downgrade. b. The upper limit of disk capacity under the corresponding specification is as displayed on the Adjust Configuration page in the console. |
Disk capacity | a. Two-node (formerly High Availability/Cluster Edition) instances of local disk edition support disk capacity expansion and reduction. b. Two-node (formerly High Availability/Cluster Edition) instances of cloud disk edition support disk capacity expansion but not reduction. c. Single-node (formerly Basic Edition) instances support disk capacity expansion but not reduction. |
Note:
If you need to horizontally scale the read capability of your database, use read-only instances to mitigate the pressure on the primary instance as instructed in Managing Read-Only Instance.
Restrictions on upgrade/downgrade
Instance Type | Disk Type | Version Upgrade | Architecture Upgrade | Specification Upgrade | Disk Capacity Expansion | Version Downgrade | Architecture Downgrade | Specification Downgrade | Disk Capacity Reduction |
Single-node (formerly Basic Edition) instance | Cloud disk | ✓ | X | ✓ | ✓ | X | X | ✓ | X |
Two-node (formerly High Availability/Cluster Edition) instance | Local disk | ✓ | ✓ | ✓ | ✓ | X | X | ✓ | ✓ |
| Cloud disk | ✓ | ✓ | ✓ | ✓ | X | X | ✓ | X |
Read-only instance | Local disk | X | X | ✓ | ✓ | X | X | ✓ | ✓ |
| Cloud disk | X | X | ✓ | ✓ | X | X | ✓ | X |
Instance disk space description
Two-node (formerly High Availability/Cluster Edition) instance - local disk
When the size of the data stored in an instance exceeds its storage space, features such as database import and rollback will become unavailable. You will need to expand its capacity or delete some database tables in the console to release the storage space. We recommend that you check the disk monitoring metrics of the instance in time as instructed in Viewing Monitoring Charts and set the alarm policy for the disk in CM, so as to prevent disk overruns from affecting your business operations.
Two-node (formerly High Availability/Cluster Edition) instance - cloud disk
When the size of the data stored in an instance exceeds its storage space, the database will become read-only. We recommend that you check the disk monitoring metrics of the instance in time as instructed in Viewing Monitoring Charts, set the alarm policy for the disk in CM, and expand the storage space or delete tables in the console promptly, so as to prevent the read-only status from affecting your business operations. The instance will become readable/writable after your expand or free up the storage space.
Single-node (formerly Basic Edition) instance - cloud disk
When the size of the data stored in an instance exceeds its storage space, the database will become read-only. We recommend that you check the disk monitoring metrics of the instance in time as instructed in Viewing Monitoring Charts, set the alarm policy for the disk in CM, and expand the storage space or delete tables in the console promptly, so as to prevent the read-only status from affecting your business operations. The instance will become readable/writable after your expand or free up the storage space.
Configuration adjustment rules
You cannot cancel a configuration adjustment operation in progress.
The name, access IP, and access port of an instance will remain the same after configuration adjustment.
Data migration may be involved in configuration adjustment. During data migration, the TencentDB for SQL Server instance can be accessed normally and the business will not be affected.
Instance switchover may be needed after configuration adjustment is completed (i.e., the TencentDB for SQL Server instance may be disconnected for seconds). We recommend that you use applications configured with automatic reconnection feature and conduct the switch during the instance maintenance time. For more information, see Setting Instance Maintenance Information.
Limits
As a single-node (formerly Basic Edition) instance has only one database node and no secondary node as a hot backup, when the node fails or performs tasks such as configuration adjustment and version upgrade, it will become unavailable for a long time. If your business has high requirements for the database availability, we recommend that you use two-node (formerly High Availability/Cluster Edition) instances instead.
Billing
Directions
Was this page helpful?
You can also Contact Sales or Submit a Ticket for help.
Yes
No