tencent cloud

All product documents
TencentDB for SQL Server
DocumentationTencentDB for SQL ServerProduct IntroductionProduct ArchitectureSingle Node (Formerly Basic Edition)
Single Node (Formerly Basic Edition)
Download PDF
Last updated: 2024-01-18 17:16:54
Single Node (Formerly Basic Edition)
Last updated: 2024-01-18 17:16:54
Download PDF
SQL Server supports two deployment architectures: single node and two-node. This document elaborates on the single node architecture.

Supported Versions

SQL Server 2008 R2, 2012, 2014, 2016, 2017, 2019, and 2022 Enterprise.

Architecture

The single node architecture is deployed using a solitary node, offering an affordable solution with impressive cost-effectiveness. Its distinguishing features include:
Decoupling of computational and storage units allows for quick recovery by switching nodes in case of computational node failures. The underlying data is stored in triplicate on cloud disks, ensuring reliable data safeguarding. In the event of disk failures, rapid restoration is made possible through disk snapshot mode.
Offering over 20 monitoring metrics, such as database connections, access, and resource usage, the single node architecture supports setting up corresponding warning strategies. This is considerably more convenient compared to a self-built CVM while also offering significant cost advantages. Deployed on a CVM, the database performance provided by a single node is superior than a user-built system.
The single node architecture leverages premium cloud disks as its underlying storage medium, making it suitable for 90% of I/O scenarios. This attribute coupled with its reliable performance and cost-effectiveness highlights its quality and value.
Note：
Single-node instances are suitable for personal learning, small-to-medium sized enterprise’s ISV software (such as financial, CRM, ERP etc. software clients), web-based applications, non-core small enterprise systems, and TEST-IMAGE environments.
As the single node architecture comprises a singular node, the recovery time following a node failure would be slightly longer than a CVM, as this process involves instance startup and data restoration.
For businesses requiring high availability, it is recommended to use two-node instances (formerly High Availability/Cluster Edition).


Was this page helpful?
You can also Contact Sales or Submit a Ticket for help.
Yes
No

Feedback

Contact Us

Contact our sales team or business advisors to help your business.

Contact Us
Technical Support

Open a ticket if you're looking for further assistance. Our Ticket is 7x24 avaliable.

Submit a Ticket
7x24 Phone Support
Hong Kong, China
+852 800 906 020 (Toll Free)
United States
+1 844 606 0804 (Toll Free)
United Kingdom
+44 808 196 4551 (Toll Free)
Canada
+1 888 605 7930 (Toll Free)
Australia
+61 1300 986 386 (Toll Free)
EdgeOne hotline
+852 300 80699
More local hotlines coming soon