Tencent Cloud

Recent Pages

Changing Network

Last updated: 2024-08-14 10:37:12

TencentDB for SQL Server supports changing the instance's network according to business needs. This document describes related operations in the SQL Server console to change the network.
 Note:
TencentDB for SQL Server supports changing only the private network address with the network unchanged. For more information, see Changing Only Private Network Addresses with Network Unchanged.
TencentDB for SQL Server supports manually releasing the old IP address when the old-address recycling time is set to non-zero during the private IP change. For more information, see Manually Releasing Reserved Addresses.
There are two types of TencentDB network environments: VPC and classic network.
Classic network: It is the public network resource pool for all Tencent Cloud users. All your Tencent Cloud resources will be centrally managed by Tencent Cloud.
VPC: It is a logically isolated network space that can be customized in Tencent Cloud. Even in the same region, different VPCs cannot communicate with each other by default. Similar to the traditional network in an IDC, a VPC is where your Tencent Cloud service resources are managed.
Scenario
Tencent Cloud supports VPC to offer a diversity of smooth services. On this basis, we provide the VPC change feature to help you manage network connectivity with ease.
﻿Scenario 1: VPC to VPC: Changing the instance's network; the private network address will change, and the application system needs to reconnect using the new private network address.
﻿Scenario 2: Only changing the private network address with network unchanged: The instance's network remains unchanged, only the private network address changes, and the application system needs to reconnect using the new private network address.
﻿Scenario 3: Manually releasing reserved addresses: When changing the internal network address and the old address recycling time is not set to 0, you can quickly release the old address and enable the new internal network address by releasing the reserved address.
Instructions for Sensitive Operations with MFA Integrated
To enhance the security of the cloud account, TencentDB for SQL Server supports MFA (Multi-Factor Authentication), which brings an extra layer of protection in addition to the username and password. After the MFA device verification is enabled, when you perform operations such as destroying instances/changing network/modifying IP addresses/resetting passwords/deleting accounts/resetting instances/performing primary-replica switch, a second identity verification based on the MFA dynamic code will be conducted. Such operations can be executed only after successful verification. For an introduction to MFA and how to enable the operation protection, see MFA Devices.
Supported instance types
VPC to VPC: primary instances (including SSIS instances), read-only instances, and replica nodes (replica node read-only addresses).
Only changing the private network address with network unchanged: primary instances (including SSIS instances) and read-only instances.
Manually releasing reserved addresses: primary instances (including SSIS instances) and read-only instances.
Note
Changing the private network IP will affect the database services currently being accessed.
Changing the network will change the instance IP. The original IP will become invalid after 24 hours by default. Modify the instance IP on the client promptly.
If Valid Hours of Old IP is set to 0, the IP will be released immediately after the network is changed.
Subnet description
A subnet is a logical network space in a VPC. You can create subnets in different AZs in the same VPC, which communicate with each other over the private network by default. Even if you select a subnet in another AZ in the same region, the network latency will not be increased because the actual business connection adopts nearby access.
Scenario 1 Operation Steps: VPC to VPC
Primary Instance/Read-Only Instance
Replica Node Read-Only Address
1. Log in to the TencentDB for SQL Server console, select the region, and click Instance ID/Name of the target instance or Manage in the Operation column.
﻿
2. In the Instance Info on the Instance Details page on the right-hand side click Change Network under the primary node or the current read-only instance.
﻿
3. In the pop-up window, select a VPC, set Valid Hours of Old IP, select Auto-Assign IP or Specify IP, and click OK.
Select Network: After a VPC is selected, only servers in it can access the database.
Valid Hours of Old IP: You can select 0–168 hours. If it is set to 0, the old IP will be repossessed immediately.
Auto-Assign IP: The system automatically assigns the new IP address.
Specify IP: You can customize the subnet IP address.
﻿
4. The VPC is changed successfully when the instance status becomes Running.
Note:
The modification of the replica node read-only address is supported only after the replica node read-only feature has been enabled. For more information on enabling the feature, see Replica Node Read-Only.
Changing the network will change the replica node read-only IP, and the original IP address will be immediately repossessed.
To change the network, you can only select the VPC network and subnet in the same region where the instance resides.
1. Log in to the SQL Server Console, select the region, and click the Instance ID / Name or Manage in the Operations column of the instance requiring network switch.
﻿
2. In the Instance Info on the Instance Details page on the right-hand side, click on Change Network under the replica node.
3. In the Change Network pop-up window, after modifying the network and read-only address, click OK.
﻿
Select Network: After a VPC network is selected, only hosts corresponding to the VPC network can access the database.
Auto-assign IP: A new IP address will be automatically assigned by the system.
Specify IP: You can customize the subnet IP address.
Scenario 2 Operation Steps: Only changing the private network address with network unchanged
1. Log in to the SQL Server Console, select the region, click the target  Instance ID/Name  or  Manage  in the Operation column.
﻿
2. In the Instance Info on the Instance Details page on the right-hand side, click the edit icon following the private network address under the primary node or the current read-only instance.
﻿
3. In the pop-up window, after modifying the private network address, click OK.
﻿
Note:
You may also navigate to the Instance Info on the Instance Details page on the right-hand side, click Change Network under the primary node or the current read-only instance. In the pop-up window, you can change the private network address simply by setting the recovery time and specifying an IP, without changing the network itself.
﻿
Scenario 3 Operation Steps: Manually releasing reserved addresses
When changing the network, if the recycling time for the old IP address is set to a non-zero hour, the old IP address will be recycled after the set time. You can also manually release the reserved address to release the old IP address in advance.
1. In the Instance Info on the Instance Details page on the right-hand side, click Release following the Reserved Address.
2. In the pop-up window, click  OK , the old IP address will be immediately released. After release, other resources can use the IP address resource in the same subnet.