Single-Node (Formerly Basic Edition)
Download
Focus Mode
Font Size
TencentDB for SQL Server supports three deployment architectures: single-node, two-node, and multi-node. This document introduces the single-node architecture.
Supported Versions
SQL Server 2012,2014,2016,2017,2019,2022,2025 Enterprise.
Architecture
The architecture of a single-node primary instance displayed in the console is shown in the following figure.
The single-node architecture uses a single-node deployment and has a relatively low usage cost. Its features are as follows:
It features a decoupled compute and storage architecture. If a compute node fails, you can quickly recover by replacing the node. The underlying data is stored on cloud disks using a triple-replica mechanism, which helps improve data reliability. In case of a disk failure, you can quickly recover using the disk snapshot mode.
The single-node architecture provides over 20 multi-dimensional monitoring metrics for database connections, access, resources, and more. Corresponding alarm policies can be configured. Compared with self-built databases on CVMs, it reduces Ops management tasks for database connections, access, and resources. It also offers a price advantage, saving cost expenditures compared to self-built databases on CVMs.
The underlying storage medium of the single-node architecture uses high-performance cloud disks. It is suitable for 90% of I/O scenarios, offering high quality, low cost, and stable performance.
Note:
The single-node architecture is suitable for personal learning, ISV software for small and medium-sized enterprises (such as finance, CRM, and ERP software), Web applications, non-core small systems of enterprises, and testing environments.
Because the single-node architecture has only one node, the recovery time after a node failure is slightly longer than that for a CVM failure (involving instance startup and data recovery).
For services that require high availability, we recommend using the two-node architecture (formerly HA Edition and Cluster Edition).
AZs Supported by the Single-Node Architecture
Region | AZ | Single-Node Cluster Edition | Read-only Cluster Edition | Read-only (Local Disk) |
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 (China) Zone 1 ap-hongkong-1 | × | × | ✓ |
| Hong Kong (China) Zone 2 ap-hongkong-2 | ✓ | ✓ | ✓ |
| Hong Kong (China) Zone 3 ap-hongkong-3 | × | ✓ | × |
Region | AZ | Single-Node Cluster Edition | Read-only Cluster Edition | Read-only (Local Disk) |
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 | ✓ | ✓ | × |
| Jakarta Zone 2 ap-jakarta-2 | ✓ | ✓ | × |
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 | AZ | Single-Node Cluster Edition | Read-only Cluster Edition | Read-only (Local Disk) |
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 | Read-only Cluster Edition | Read-only (Local Disk) |
Middle East (Riyadh) me-riyadh | Riyadh Zone 1 me-saudi-arabia-1 | ✓ | ✓ | × |
| Riyadh Zone 2 me-saudi-arabia-2 | ✓ | ✓ | × |
Help and Support
Was this page helpful?
You can also Contact sales or Submit a Ticket for help.
Help us improve! Rate your documentation experience in 5 mins.
Feedback