TencentDB for SQL Server is licensed by Microsoft to continuously provide you with the latest features, so you can avoid any risks arising from unauthorized software use. It features out-of-the-box usage, high stability, reliability, and security, elastic scaling, data security protection, and failover in seconds, allowing you to focus on application development.
Note：
As one of the earliest commercial database products, SQL Server supports complex SQL queries with excellent performance. Thanks to its comprehensive support for applications based on the Windows .NET Framework, it is widely used in such fields as government services, finance, healthcare, retail, education, and gaming.
Deployment Architecture
TencentDB for SQL Server supports 3 types of instance deployment architectures: single-node, two-node, and multi-node.
Single-Node (Formerly Basic Edition)
The single-node architecture has only one compute node. It is highly cost-effective and opens the highest SA permissions. It applies to lightweight scenarios. The core strengths lie in low cost and high-level permissions. In case of a compute node failure, the business can be recovered by replacing the node. When a disk failure occurs, the data can be rebuilt by using a disk snapshot, which takes a relatively long time. This architecture is mainly used in personal learning environments, non-core small systems of enterprises, and development and testing environments to meet the flexible needs of low-load and non-critical businesses. The instance architecture displayed in the console is Single-Node (Cloud Disk).
Two-Node (Formerly HA/Cluster Edition)
The two-node architecture adopts a high-availability design with one primary node and one secondary node. The primary node provides read/write services, while the secondary node synchronizes data in real-time but is inaccessible. (The secondary node in the cloud disk architecture can be accessed.) For SQL Server 2008R2, 2012, 2014, and 2016 Enterprise, the primary/secondary two-node architecture consists of one primary SQL Server database and a mirror SQL Server database. For SQL Server 2017, 2019, and 2022 Enterprise, the primary/secondary two-node architecture adopts the Always On architecture. The second-level automatic failover and multi-AZ disaster recovery capabilities ensure business continuity and data security. It has high performance and applies to high-concurrency scenarios, such as e-commerce transactions, financial payments, multi-tenancy SaaS, and online game services, making it an ideal choice for core production systems of enterprises. Depending on the selected storage type, the instance architecture displayed in the console is Two-Node (Local Disk) or Two-Node (Cloud Disk).
Multi-Node
The multi-node architecture adopts the Always On architecture design of one-primary-multiple-secondary + compute-storage separation. SQL Server 2017, 2019, and 2022 Enterprise are supported. The primary node provides read/write services, while the secondary nodes provide read-only services and can be switched to the primary node within seconds. This achieves multi-AZ disaster recovery and elastic scalability. By dynamically adding or removing nodes and adjusting resources on demand, this architecture can meet the high performance requirements of massive data reads, frequent scaling, and multi-active disaster recovery. In addition, it complies with the strict regulatory requirements of finance, government affairs, and other industries. It applies to complex businesses (such as real-time analysis and multi-tenancy systems) and high performance scenarios requiring read-write separation and can balance business flexibility and stability. The instance architecture displayed in the console is Multi-Node (Cloud Disk).
Isolation Policy
The single-node (cloud disk), two-node (cloud disk), and multi-node (cloud disk) instances for TencentDB for SQL Server are deployed based on the CVM. Each instance exclusively occupies one CVM, with dedicated CPU, memory, and disk resources, ensuring complete isolation between different instances.
The two-node (local disk) instances for TencentDB for SQL Server are deployed on local physical servers. Multiple instances are deployed on each physical server. Isolation policies are implemented to ensure complete isolation between different instances, guaranteeing exclusive use of CPU, memory, and disk resources.
In addition, TencentDB for SQL Server has also implemented corresponding data isolation policies across multiple dimensions, including accounts, regions, AZs, and networks.