tencent cloud

TencentDB for SQL Server

Release Notes and Announcements
Release Notes
Product Announcements
User Guide
Product Introduction
Overview
Product Architecture
Strengths
Use Cases
Regions and AZs
Major Version Lifecycle Explanation
Features and Differences
Instance Types
Instance Specifications
Storage Types
Common Concepts
Network Environment
License Statement
Purchase Guide
Billing Overview
Product Pricing
Purchase Methods
Renewal Instructions
Payment Overdue
Refund
From Pay-as-You-Go to Monthly Subscription
Instance Adjustment Fees Description
Local Backup Space Billing
Cross-Region Backup Billing
Viewing Bill Details
Getting Started
Creating TencentDB for SQL Server Instance
Connecting to TencentDB for SQL Server Instance
Managing TencentDB for SQL Server Instance
Operation Guide
Constraints and Limits
Usage Specifications and Suggestions
Maintaining Instance
Adjusting Instance Configuration
Read-Only Instance
Network and Security
Account Management
Database Management
Data Security
Parameter Configuration
Monitoring and Alarms
Backup and Restoration 
Log Management
Publish-Subscribe
SSIS
Data Migration (New)
Data Migration (Legacy)
Data Synchronization (DTS) 
Practical Tutorial
TencentDB for SQL Server Methods for Regular Maintenance
TencentDB for SQL Server Optimization of Slow SQL
How to Better Use Tempdb
Cross-Account Backup Restoration
Creating VPC for TencentDB for SQL Server
Connecting Kingdee K/3 WISE to TencentDB for SQL Server
Account Permissions and Permission Control
Enabling and Disabling the CDC Feature
Shrinking a Database
API Documentation
History
Introduction
API Category
Making API Requests
Sales and fee related APIs
Instance Management related APIs
Operation and maintenance management related APIs
Network management related APIs
Account management related APIs
Database management related APIs
Security group management related APIs
Data security encryption related APIs
Parameter configuration related APIs
Extended Event related APIs
Log management related APIs
Read only instance management related APIs
Publish and subscribe related APIs
Backup related APIs
Rollback related APIs
Data migration (cold standby migration) related APIs
SQL Server Integration Services (SSIS) related APIs
Data migration (DTS old version) related APIs
Data Types
Error Codes
FAQs
Overview
Model Selection
Pricing and Selection
Connection and Network
Account and Permission
Backup and Rollback
Data Migration
Publish/Subscribe
Read-Only Instance
Version and Architecture Upgrade
Disk Space and Specification Adjustment
Monitoring and Alarms
Log-Related
Parameter Modification
Features
Performance, Space, and Memory-Related FAQs
Service Agreement
Service Level Agreement
Terms of Service
Performance Evaluation
Performance Test Report
Glossary
Contact Us

Regions and AZs

PDF
フォーカスモード
フォントサイズ
最終更新日: 2026-01-14 11:01:59

Region

Overview

A region is the physical location of an IDC. In Tencent Cloud, regions are fully isolated from each other, ensuring cross-region stability and fault tolerance. When purchasing Tencent Cloud services, we recommend selecting the region closest to your end users to minimize access latency and improve download speed.

Characteristics

The networks of different regions are fully isolated from each other, and Tencent Cloud services in different regions cannot communicate using private networks by default.
Tencent Cloud services in different VPCs can communicate with each other over Cloud Connect Network which is fast and stable.
Cloud Load Balancer currently supports intra-region traffic forwarding by default. If cross-region binding is enabled, cross-region binding of CLB and TencentDB instances is supported.

AZ

Overview

An availability zone (AZ) is a physical IDC of Tencent Cloud with independent power supply and network in the same region. It can ensure business stability, as failures (except for major disasters or power failures) in one AZ are isolated without affecting other AZs in the same region. By starting an instance in an independent AZ, users can protect their applications from being affected by a single point of failure.

Characteristics

Tencent Cloud services in the same VPC are interconnected over the private network, which means they can communicate using private IPs, even if they are in different AZs of the same region.
Note:
Private network interconnection refers to the interconnection of resources under the same account. Resources under different accounts are completely isolated on the private network.

China

Region
AZ
South China (Guangzhou)
ap-guangzhou
Guangzhou Zone 3
ap-guangzhou-3
Guangzhou Zone 4 (sold out)
ap-guangzhou-4
Guangzhou Zone 6
ap-guangzhou-6
Guangzhou Zone 7
ap-guangzhou-7
South China ( Shenzhen Finance ) ap-shenzhen-fsi
Shenzhen Finance Zone 1 (only available for financial institutions and enterprises Submit a ticket to apply for activation.) ap-shenzhen-fsi-1
East China (Shanghai)
ap-shanghai
Shanghai Zone 2
ap-shanghai-2
Shanghai Zone 3
ap-shanghai-3
Shanghai Zone 4
ap-shanghai-4
Shanghai Zone 5
ap-shanghai-5
East China (Nanjing)
ap-nanjing
Nanjing Zone 1
ap-nanjing-1
Nanjing Zone 2
ap-nanjing-2
East China (Shanghai Finance)
ap-shanghai-fsi
Shanghai Finance Zone 1 (only for financial institutions and enterprises; submit a ticket to apply for support.) (sold out)
ap-shanghai-fsi-1
Shanghai Finance Zone 3 (only for financial institutions and enterprises; submit a ticket to apply for support.)
ap-shanghai-fsi-3
Shanghai Finance Zone 4 (only for financial institutions and enterprises; submit a ticket to apply for support.)
ap-shanghai-fsi-4
North China (Beijing)
ap-beijing
Beijing Zone 1
ap-beijing-1
Beijing Zone 3
ap-beijing-3
Beijing Zone 4
ap-beijing-4
Beijing Zone 5
ap-beijing-5
Beijing Zone 6
ap-beijing-6
Beijing Zone 7
ap-beijing-7
North China (Beijing Finance)
ap-beijing-fsi
Beijing Finance Zone 1 (only for financial institutions and enterprises; submit a ticket to apply for support.)
ap-beijing-fsi-1
Beijing Finance Zone 2 (only for financial institutions and enterprises; submit a ticket to apply for support.)
ap-beijing-fsi-2
Southwest China (Chengdu)
ap-chengdu
Chengdu Zone 1
ap-chengdu-1
Chengdu Zone 2
ap-chengdu-2
Southwest China (Chongqing)
ap-chongqing
Chongqing Zone 1
ap-chongqing-1
North China ( Beijing Finance ) ap-beijing-fsi
Beijing Finance Zone 1 (only available for financial institutions and enterprises Submit a ticket to apply for activation.) ap-beijing-fsi-1
Hong Kong/Macao/Taiwan (Hong Kong, China)
ap-hongkong
Hong Kong Zone 1 (Hong Kong nodes cover services in the China regions of Hong Kong, Macao, and Taiwan)
ap-hongkong-1
Hong Kong Zone 2 (Hong Kong nodes cover services in the China regions of Hong Kong, Macao, and Taiwan)
ap-hongkong-2
Hong Kong Zone 3 (Hong Kong nodes cover services in the China regions of Hong Kong, Macao, and Taiwan)
ap-hongkong-3

Other Countries and Regions

Region
Availability Zone
Southeast Asia (Singapore)
ap-singapore
Singapore Zone 1 (Singapore nodes can cover services in Southeast Asia)
ap-singapore-1
Singapore Zone 2 (Singapore nodes can cover services in Southeast Asia)
ap-singapore-2
Singapore Zone 3 (Singapore nodes can cover services in Southeast Asia)
ap-singapore-3
Singapore Zone 4 (Singapore nodes can cover services in Southeast Asia)
ap-singapore-4
Southeast Asia ( Jakarta )
ap-jakarta
Jakarta Zone 1 (Jakarta nodes can cover services in Southeast Asia)
ap-jakarta-1
Jakarta Zone 2 (Jakarta nodes can cover services in Southeast Asia) ap-jakarta-2
Southeast Asia (Bangkok)
ap-bangkok
Bangkok Zone 1 (Bangkok nodes can cover services in Southeast Asia)
ap-bangkok-1
Bangkok Zone 2 (Bangkok nodes can cover services in Southeast Asia)
ap-bangkok-2
Northeast Asia (Seoul)
ap-seoul
Seoul Zone 1 (Seoul nodes can cover services in Northeast Asia)
ap-seoul-1
Seoul Zone 2 (Seoul nodes can cover services in Northeast Asia)
ap-seoul-2
Northeast Asia (Tokyo)
ap-tokyo
Tokyo Zone 1 (Tokyo nodes can cover services in Northeast Asia)
ap-tokyo-1
Tokyo Zone 2 (Tokyo nodes can cover services in Northeast Asia)
ap-tokyo-2
US West (Silicon Valley)
na-siliconvalley
Silicon Valley Zone 1 (Silicon Valley nodes can cover services in West US)
na-siliconvalley-1
Silicon Valley Zone 2 (Silicon Valley nodes can cover services in West US)
na-siliconvalley-2
East US (Virginia)
na-ashburn
Virginia Zone 1 (Virginia nodes can cover services in East US)
na-ashburn-1
Virginia Zone 2 (Virginia nodes can cover services in East US)
na-ashburn-2
Europe (Frankfurt)
eu-frankfurt
Frankfurt Zone 1 (Frankfurt nodes can cover services in Europe)
eu-frankfurt-1
Frankfurt Zone 2 (Frankfurt nodes cover services in Europe)
eu-frankfurt-2
South America (São Paulo)
sa-saopaulo
São Paulo Zone 1 (São Paulo nodes can cover services in South America)
sa-saopaulo-1
Middle East (Riyadh)
me-riyadh
Riyadh Zone 1
me-saudi-arabia-1
Riyadh Zone 2
me-saudi-arabia-2

Availability Zones Supported by Each Version of the Architecture

China
Asia Pacific
Europe and Americas
Middle East
Region
Availability Zone
Multi-Node Cloud Disk Edition
Cloud Disk Edition Single Node
Cloud Disk Edition Two-Node
Cloud Disk Edition RO
Local Disk Two-Node
Local Disk RO
Guangzhou
ap-guangzhou
Guangzhou Zone 3
ap-guangzhou-3
×
×
Guangzhou Zone 6
ap-guangzhou-6
×
Guangzhou Zone 7
ap-guangzhou-7
×
Shanghai
ap-shanghai
Shanghai Zone 2
ap-shanghai-2
Shanghai Zone 3
ap-shanghai-3
×
×
Shanghai Zone 4
ap-shanghai-4
Shanghai Zone 5
ap-shanghai-4
×
Shanghai Finance
ap-shanghai-fsi
Shanghai Finance Zone 3
ap-shanghai-fsi-3
×
×
×
Shanghai Finance Zone 4
ap-shanghai-fsi-4
×
×
×
Nanjing
ap-nanjing
Nanjing Zone 1
ap-nanjing-1
×
Nanjing Zone 2
ap-nanjing-2
×
Beijing
ap-beijing
Beijing Zone 1
ap-beijing-1
×
×
×
×
Beijing Zone 3
ap-beijing-3
Beijing Zone 4
ap-beijing-4
×
×
×
×
×
Beijing Zone 5
ap-beijing-5
×
×
Beijing Zone 6
ap-beijing-6
×
Beijing Zone 7
ap-beijing-7
×
Beijing Finance
ap-beijing-fsi
Beijing Finance Zone 1
ap-beijing-fsi-1
×
×
×
Beijing Finance Zone 2
ap-beijing-fsi-2
×
×
×
Chengdu
ap-chengdu
Chengdu Zone 1
ap-chengdu-1
×
×
Chengdu Zone 2
ap-chengdu-2
×
×
Chongqing
ap-chongqing
Chongqing Zone 1
ap-chongqing-1
×
×
Hong Kong (China)
ap-hongkong
Hong Kong Zone 1
ap-hongkong-1
×
×
×
×
Hong Kong (China) Zone 2
ap-hongkong-2
×
Hong Kong Zone 3
ap-hongkong-3
×
×
×
Region
Availability Zone
Cloud Disk Edition Single Node
Cloud Disk Edition Two-Node
Cloud Disk Edition RO
Local Disk Two-Node
Local Disk RO
Singapore
ap-singapore
Singapore Zone 1
ap-singapore-1
×
×
×
×
Singapore Zone 2
ap-singapore-2
×
×
×
×
Singapore Zone 3
ap-singapore-3
×
×
×
Singapore Zone 4
ap-singapore-4
×
×
×
Jakarta
ap-jakarta
Jakarta Zone 1
ap-jakarta-1
×
×
×
×
Bangkok
ap-bangkok
Bangkok Zone 1
ap-bangkok-1
×
×
×
×
Bangkok Zone 2
ap-bangkok-2
×
×
×
×
Seoul
ap-seoul
Seoul Zone 1
ap-seoul-1
×
Seoul Zone 2
ap-seoul-2
×
×
Tokyo
ap-tokyo
Tokyo Zone 1
ap-tokyo-1
×
×
Tokyo Zone 2
ap-tokyo-2
×
×
Region
Availability Zone
Cloud Disk Edition Single Node
Cloud Disk Edition Two-Node
Cloud Disk Edition RO
Local Disk Two-Node
Local Disk RO
Virginia
na-ashburn
Virginia Zone 1
na-ashburn-1
×
×
×
Virginia Zone 2
na-ashburn-2
×
×
×
Frankfurt
eu-frankfurt
Frankfurt Zone 1
eu-frankfurt-1
×
×
×
Frankfurt Zone 2
eu-frankfurt-2
×
×
×
Silicon Valley
na-siliconvalley
Silicon Valley Zone 1
na-siliconvalley-1
×
×
Silicon Valley Zone 2
na-siliconvalley-2
×
×
São Paulo
sa-saopaulo
São Paulo Zone 1
sa-saopaulo-1
×
×
×
Region
AZ
Single-Node Cluster Edition
Two-Node Cluster Edition
Read-only Cluster Edition
Two-Node (Local Disk)
Read-only (Local Disk)
Middle East (Riyadh)
me-riyadh
Riyadh Zone 1
me-saudi-arabia-1
×
×
Riyadh Zone 2
me-saudi-arabia-2
×
×

Selection of Regions and AZs

The geographic locations of TencentDB instances, your business, and your target users.
We recommend you choose the region closest to your end users when purchasing TencentDB instances to minimize access latency and improve access speed.
Other Tencent Cloud services you use.
When you select other Tencent Cloud services, we recommend you try to locate them all in the same region and AZ to allow them to communicate with each other through the private network, reducing access latency and increasing access speed.
High availability and disaster recovery.
Even if you have just one VPC, we still recommend you deploy your businesses in different AZs to prevent a single point of failure and enable cross-AZ disaster recovery.
There may be network latency among different AZs. We recommend you assess your business requirements and find the optimal balance between high availability and low latency.
If you need access to servers in other countries or regions, we recommend you select an instance in those other countries or regions. If you use a TencentDB instance in China to access servers in other countries and regions, you may encounter a higher network latency.

Resource Availability

The following table describes which resources are global, which are regional, and which are specific to AZs.
Resources
Resource ID Format <Resource abbreviation>-8-Digit String of Numbers and Letters
Type
Description
User account
No restrictions
Globally unique
A user can use the same account to access Tencent Cloud resources worldwide.
SSH Key
skey-xxxxxxxx
Available in all regions
A user can use an SSH key to bind to any region's CVM under the account.
ins-xxxxxxxx
Can only be used in a single availability zone within a single region.
Users can only create CVM instances in specific availability zones.
img-xxxxxxxx
Available in a single region and multiple availability zones
Users can create a custom image for an instance and use it across different Availability Zones within the same region. To use the image in other regions, please use the image replication feature to copy the custom image to other regions.
eip-xxxxxxxx
Available in a single region and multiple availability zones
Elastic IP addresses are created within a specific region and can only be associated with instances in the same Region.
sg-xxxxxxxx
Available in a single region and multiple availability zones
Security groups are created within a specific region and can only be associated with instances in the same Region. Tencent Cloud automatically creates three default security groups for users.
disk-xxxxxxxx
Can only be used in a single availability zone within a single region.
Users can only create CBS in a specific availability zone and attach them to instances in the same availability zone.
snap-xxxxxxxx
Available in a single region and multiple availability zones
After creating a snapshot for a specific CBS, the user can use the snapshot for other operations (such as creating a CBS) in the same region.
 CLB 
clb-xxxxxxxx
Available in a single region and multiple availability zones
CLB can be bound to CVM instances in different availability zones within the same region for traffic forwarding.
vpc-xxxxxxxx
Available in a single region and multiple availability zones
VPC is created in a specific region and resources belonging to the same VPC can be created in different availability zones.
subnet-xxxxxxxx
Can only be used in a single availability zone within a single region.
Users cannot create subnets across availability zones.
rtb-xxxxxxxx
Available in a single region and multiple availability zones
When creating a routing table, users need to specify a specific VPC, thus it follows the location attribute of the VPC.
TencentDB for SQL Server supports cross-AZ instance migration. For more information, see Migrating Across AZs.

ヘルプとサポート

この記事はお役に立ちましたか?

フィードバック