Adjusting Instance Specifications
Download
フォーカスモード
フォントサイズ
Instance Specifications
For detailed information on the instance specifications and pricing supported by TencentDB for SQL Server, see Product Specifications.
Prerequisites
You can initiate the configuration adjustment operation only when your TencentDB for SQL Server instance and its associated instances are in a normal state (Running) and no tasks are being executed.
Specification Change Process
Specification Scaling Scenario
After you adjust configurations in the console, the system determines whether to complete the change through in-place scaling or data migration. The configuration adjustment process is as follows:
Impact of Specification Changes
Note:
TencentDB for SQL Server cloud disk edition instances do not support capacity expansion of disks.
When you perform operations such as cross-AZ migration / instance specification adjustment / instance edition upgrade that trigger a data migration scenario, system databases are not migrated. Do not create business-related data under system databases to avoid data loss after migration. Furthermore, under the aforementioned operation scenarios, non-standard system database operations and instance-level operations are not migrated together. You must handle them manually after the migration is completed.
Single-Item Specification Change
Single-item configuration adjustment refers to adjusting only the specification or the disk. The impact of the configuration adjustment is as follows:
Instance Architecture | Disk Type | Adjustment Item | Adjustment Decision | Adjustment Impact | Time |
Single-Node (Formerly Basic Edition) | Cloud disk | Specification upgrade, disk capacity expansion, or specification downgrade | Upgrade, expand, or downgrade | Disk capacity expansion: 1. The instance will perform in-place capacity expansion during the configuration adjustment. 2. During this period, no instance restart or momentary disconnection will occur, and the business will not be affected. 3. You can set the effective time, which is the actual configuration change time. Upgrade or downgrade of the instance specifications: 1. The instance will be restarted during configuration adjustment. 2. The service will be unavailable for about 1 to 3 minutes. 3. Perform the adjustment during off-peak hours allowed by the business. | You need to select the time for the new configuration to take effect. |
Two-Node (Formerly HA/Cluster Edition) | Local Disk | Disk scale-in | In-place Downgrade | 1. The instance will be scaled in in-place during the configuration adjustment. 2. Data migration, instance restart, or momentary disconnection will not occur during this period. 3. You can set the effective time, which will not affect businesses. The time is the actual configuration change time. | You need to select the time for the new configuration to take effect. |
| | Specification downgrade | In-place Downgrade | 1. The instance will be scaled in in-place during the configuration adjustment. 2. The service will be unavailable for about 1 minute. 3. Perform the adjustment during off-peak hours allowed by the business. | You need to select the time for the new configuration to take effect. |
| | Specification upgrade or disk capacity expansion | Migration Upgrade | 1. During the configuration adjustment process, the instance will be migrated and scaled out. A larger data volume results in a longer data migration time. During this period, access to the instance is not affected. 2. A switch will be performed after migration is completed. During the switch, a second-level momentary database disconnection will occur. Ensure that your business application has a reconnection mechanism. 3. During the momentary disconnection, most operations related to databases, accounts, and networks cannot be performed. Ensure that you perform the switch operation during off-peak hours. | You need to select the time for the new configuration to take effect. |
| | Specification upgrade or disk capacity expansion | In-place Upgrade | 1. The instance will be scaled out in-place during the configuration adjustment. 2. Data migration, instance restart, or momentary disconnection will not occur during this period. 3. You can set the effective time, which will not affect businesses. The time is the actual configuration change time. | You need to select the time for the new configuration to take effect. |
Two-Node (Formerly HA/Cluster Edition) | Cloud disk | Specification upgrade, disk capacity expansion, or specification downgrade | Migration and Upgrade/Downgrade | Disk capacity expansion: 1. The instance will perform in-place capacity expansion during the configuration adjustment. 2. Instance restart or momentary disconnection will not occur during this period. 3. You can set the effective time, which will not affect businesses. The time is the actual configuration change time. Upgrade or downgrade of the instance specifications: 1. The instance will be restarted during configuration adjustment. 2. The service will be unavailable for about 1 to 3 minutes. 3. Perform the adjustment during off-peak hours allowed by the business. | You need to select the time for the new configuration to take effect. |
Multi-Node | Cloud disk | Specification upgrade, disk capacity expansion, or specification downgrade | Upgrade, expand, or downgrade | Disk capacity expansion: 1. The instance will perform in-place capacity expansion during the configuration adjustment. 2. Instance restart or momentary disconnection will not occur during this period. 3. You can set the effective time, which will not affect businesses. The time is the actual configuration change time. Upgrade or downgrade of the instance specifications: 1. The instance will be restarted during configuration adjustment. 2. The service will be unavailable for about 1 to 3 minutes. 3. Perform the adjustment during off-peak hours allowed by the business. | You need to select the time for the new configuration to take effect. |
Combined Specification Change
Combined configuration adjustment refers to simultaneously adjusting the specification and the disk. The impact of the configuration adjustment is as follows:
Instance Architecture | Disk Type | Adjustment Item | Adjustment Decision | Adjustment Impact | Time |
Single-Node (Formerly Basic Edition) | Cloud disk | Disk capacity expansion + specification upgrade or downgrade | Upgrade, expand, or downgrade | 1. The instance will be restarted during configuration adjustment. 2. The service will be unavailable for about 1 to 3 minutes. 3. Perform the adjustment during off-peak hours allowed by the business. | You need to select the time for the new configuration to take effect. |
Two-Node (Formerly HA/Cluster Edition) | Local Disk | Specification upgrade + disk capacity expansion | In-place Upgrade | 1. The instance will perform in-place capacity expansion during the configuration adjustment. 2. Data migration, instance restart, or momentary disconnection will not occur during this period. 3. You can set the effective time, which will not affect businesses. The time is the actual configuration change time. | You need to select the time for the new configuration to take effect. |
| | Specification upgrade + disk capacity expansion | Migration Upgrade | 1. During the configuration adjustment process, the instance will be migrated and scaled out. A larger data volume results in a longer data migration time. During this period, access to the instance is not affected. 2. A switch will be performed after migration is completed. During the switch, a second-level momentary database disconnection will occur. Ensure that your business application has a reconnection mechanism. 3. During the momentary disconnection, most operations related to databases, accounts, and networks cannot be performed. Ensure that you perform the switch operation during off-peak hours. | You need to select the time for the new configuration to take effect. |
| | Specification upgrade + disk scale-in | Upgrade, expand, or downgrade | 1. The instance will perform in-place capacity expansion during the configuration adjustment. 2. Data migration, instance restart, or momentary disconnection will not occur during this period. 3. You can set the effective time, which will not affect businesses. The time is the actual configuration change time. | Effective time is selectable. |
| | Specification upgrade + disk scale-in | Migration and Upgrade/Downgrade | 1. During the configuration adjustment process, the instance will be migrated and scaled out. A larger data volume results in a longer data migration time. During this period, access to the instance is not affected. 2. A switch will be performed after migration is completed. During the switch, a second-level momentary database disconnection will occur. Ensure that your business application has a reconnection mechanism. 3. During the momentary disconnection, most operations related to databases, accounts, and networks cannot be performed. Ensure that you perform the switch operation during off-peak hours. | You need to select the time for the new configuration to take effect. |
| | Specification downgrade + disk capacity expansion | May be in-place upgrade/downgrade or migration upgrade/downgrade | 1. During the configuration adjustment process, the instance may experience service unavailability for approximately one minute and may be migrated and scaled out. A larger data volume results in a longer data migration time. During this period, access to the instance is not affected. 2. A switch will be performed after migration is completed. During the switch, a second-level momentary database disconnection will occur. Ensure that your business application has a reconnection mechanism. 3. During the momentary disconnection, most operations related to databases, accounts, and networks cannot be performed. Ensure that you perform the switch operation during off-peak hours. | You need to select the time for the new configuration to take effect. |
| | Specification downgrade + disk scale-in | In-place Downgrade | 1. The instance will be scaled in in-place during the configuration adjustment. 2. The service will be unavailable for about 1 minute. 3. Perform the adjustment during off-peak hours allowed by the business. | You need to select the time for the new configuration to take effect. |
Two-Node (Formerly HA/Cluster Edition) | Cloud disk | Disk capacity expansion + specification upgrade or downgrade | Upgrade, expand, or downgrade | 1. The instance will be restarted during configuration adjustment. 2. The service will be unavailable for about 1 to 3 minutes. 3. Perform the adjustment during off-peak hours allowed by the business. | You need to select the time for the new configuration to take effect. |
Multi-Node | Cloud disk | Disk capacity expansion + specification downgrade | Upgrade, expand, or downgrade | 1. The instance will be restarted during configuration adjustment. 2. The service will be unavailable for about 1 to 3 minutes. 3. Perform the adjustment during off-peak hours allowed by the business. | You need to select the time for the new configuration to take effect. |
Operation Steps
When you perform configuration adjustments on an instance, the prompts and notes differ between instances with cloud disk and local disk architectures. For details, see the description below.
If an instance switch is involved, second-level database disconnection occurs during the instance switch, and most operations related to databases, accounts, and networks cannot be performed during this period. Ensure that the business has a reconnection mechanism.
If an instance switch is involved, you can initiate the switch within the maintenance time or immediately after migration. Ensure that the switch is performed in off-peak hours.
If the instance deployed on a local disk involves disk scale-in, the disk space after scale-in should be greater than or equal to 2 times the maximum disk space used in the past 7 days to prevent scale-in failures. For example, if an instance used 5 GB of disk space in the past 7 days, the disk space after instance scale-in should be greater than or equal to 10 GB.
If the instance deployed on a local disk involves memory scale-in, the service will be unavailable for about 1 minute. You can initiate the scale-in during the maintenance time or immediately. Operate during off-peak hours allowed by the business.
If the instance to be upgraded is associated with other instances (read-only instances), submit a ticket to contact us for solutions.
For the single-node, two-node, or multi-node instances of the TencentDB for SQL Server cloud disk architecture, the instance will be restarted after specification scale-in/out, resulting in service unavailability for approximately 1 to 3 minutes. You can initiate the adjustment immediately or within the maintenance time. Operate during off-peak hours allowed by the business.
During disk scale-out in the single-node, two-node, or multi-node instances of the TencentDB for SQL Server cloud disk architecture, no instance restart or momentary disconnection will occur, and the business will not be affected. You can select the effective time, which is the actual configuration change time.
The single-node, two-node, or multi-node instances of the TencentDB for SQL Server cloud disk architecture do not support disk scale-in.
1. Log in to the TencentDB for SQL Server console. Select the region where the instance is located, locate the corresponding instance in the instance list, and click More > Adjust Configuration in its Operation column.
2. In the pop-up configuration adjustment window, select the CPU/memory and disk capacity to be changed under the specification and disk capacity options. After verifying the settings, click OK.
Note:
Select the Time to Take Effect for the configuration change and check the orange prompt. Only migration and upgrade/downgrade scenarios require checking.
Within maintenance time: Indicates that the change will take effect within the maintenance time. You can modify the maintenance time on the instance details page.
Adjust now: Indicates that the change will take effect immediately after submission.
Due to business security and risk control requirements, the system may prompt you to restart the instance to lift the feature limitations when you perform the instance specification adjustment operation and data migration is involved. At this point, follow the prompt in the console to complete the instance restart before you perform the instance specification adjustment operation.
3. For yearly/monthly subscription instances, confirm the configuration information and fees in the redirected payment window, and click Submit Order. For pay-as-you-go instances, confirm the configuration information and fees in the redirected window, and click Adjust.
4. Return to the instance list. When the instance status changes from Switching (after configuration adjustment) to Running, the specification upgrade is complete. You can then query and confirm the new specification configuration of the instance on the Instance List or the Instance Details page.
Related APIs
API | Description |
This API is used to pre-check the impact of instance configuration changes before they are applied. | |
This API is used to upgrade instances. | |
This API can immediately complete the instance upgrade and switchover operation when the instance status is "Upgrade Pending Switchover" after expansion is initiated, without waiting for a maintenance window. |
フィードバック