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
ドキュメントTencentDB for SQL ServerProduct IntroductionProduct ArchitectureDifferences Between Local Disk Architecture and Cloud Disk Architecture

Differences Between Local Disk Architecture and Cloud Disk Architecture

PDF
フォーカスモード
フォントサイズ
最終更新日: 2025-10-11 09:58:52
TencentDB for SQL Server supports three types of instance deployment architectures: single-node, two-node, and multi-node. These instance deployment architectures are divided into local disk architecture and cloud storage architecture based on the storage type. This document describes the differences between the local disk architecture and the cloud disk architecture of TencentDB for SQL Server.

Supported Storage Types and Database Versions of Instance Deployment Architectures

You need to understand the instance deployment architectures provided by the product and the corresponding storage types and database versions supported for deployment. The following table lists the supported storage types and database versions of different instance deployment architectures. You can configure them when creating an instance as needed. In addition, you can also directly learn about instance deployment architectures on the purchase page.
Instance Deployment Architecture
Supported Storage Type
Supported Database Version
Architecture Displayed in the Console
Single-node (non-read-only instance)
Premium Disk
Cloud SSD
Balanced SSD
Enhanced SSD
SQL Server 2012/2014/2016/2017/2019/2022 Enterprise
Single-node (cloud disk)
Single-node (read-only instance)
High-performance local SSD
SQL Server 2012/2014/2016/2017/2019/2022 Enterprise
Read-only instance (local disk)
Balanced SSD
Enhanced SSD
Read-only instance (cloud disk)
Two-node
High-performance local SSD
SQL Server 2012/2014/2016/2017/2019 Enterprise
Two-node (local disk)
Balanced SSD
Enhanced SSD
SQL Server 2017/2019/2022 Enterprise
Two-node (cloud disk)
Multi-node
High-performance local SSD
(Submit a ticket for application.)
SQL Server 2017/2019/2022 Enterprise
Multi-node (local disk)
Balanced SSD
Enhanced SSD
Multi-node (cloud disk)
After learning about the instance deployment architectures, you can select a storage type for mounting to your instance. Generally, TencentDB for SQL Server can offer genuinely authorized, stable, high-performance, and highly reliable database services, regardless of whether you select local disks or cloud disks. The local disk architecture and cloud storage architecture vary slightly in performance, supported features, and other aspects. For details, see the following descriptions.

Differences Between Local Disk Architecture and Cloud Disk Architecture

Difference 1: Performance

The performance of instances with the local disk architecture differs from that of instances with the cloud disk architecture. For details, see Performance Test Report.

Difference 2: Features

Both the local disk architecture and the cloud disk architecture support common features, such as instance creation, instance connection, database creation, and account creation. However, the cloud disk architecture also supports the following features.
Architecture Type
Additional Supported Feature Compared with the Local Disk Architecture
Description
Cloud disk architecture
Supports more regions outside the Chinese mainland for deployment.
For details, see Regions and AZs.
Included regions: São Paulo, Virginia, Frankfurt, Singapore, Jakarta, and Bangkok.
If replica node read-only is enabled, replica nodes can be accessed through their unique read-only addresses, which can reduce the read request load of the primary node and effectively save read-only instance costs.
A primary-replica switch can be triggered manually when an instance fault occurs to switch the secondary database to the primary database, ensuring system availability and data integrity.
Supports later editions.
SQL Server 2022 Enterprise is supported.
Supports directly modifying the instance-level character set collation during instance creation.
The instance-level character set collation can be modified during instance creation to meet users' self-service setting needs for the default character set.
Supports directly modifying the system time zone during instance creation.
The system time zone can be modified during instance purchase to meet the needs of customers outside the Chinese mainland for the local time zone.
Supports disk encryption.
Data can be stored on disks in ciphertext. When data is read from or written to disks, it can be automatically encrypted or decrypted, enhancing data storage security.

Difference 3: Impact of Configuration Adjustments

The impacts of configuration adjustments are different between the local disk architecture and the cloud disk architecture. The specific impacts are as follows.
Local disk architecture: If local resources are sufficient during a specification upgrade or disk capacity expansion, an in-place upgrade is performed on the instance, without affecting the business. If local resources are insufficient, an upgrade through migration is performed on the instance. The migration time consumption depends on data volume. After migration, a switch is performed, causing a second-level momentary disconnection from the database. Ensure the business has a reconnection mechanism.
Cloud disk architecture: During disk capacity expansion on an instance, in-place expansion is performed on the instance, without triggering a restart or momentary disconnection. This avoids impact on the business. During an upgrade or a downgrade of specifications (CPU and memory), the instance is restarted, resulting in service unavailability for approximately 1 to 3 minutes. Perform the operation during off-peak hours of the business.

Difference 4: Number of Replica Nodes

The difference in the number of replica nodes only exists between the multi-node (local disk) architecture and the multi-node (cloud disk) architecture. The specific difference is as follows.
Multi-node (local disk): To purchase an instance of this architecture, submit a ticket for application first. You can consult the supported number of replica nodes under this architecture using the ticket.
Multi-node (cloud disk): The number of supported replica nodes ranges from 2 to 5. When configuring replica nodes in the console or on the purchase page, you can select any AZ that is not sold out in the selected region.

Difference 5: Maximum Storage Space

Currently, the maximum storage space is 6,000 GB for the local disk architecture and 32,000 GB for the cloud disk architecture.

Summary

Both TencentDB for SQL Server instances with the local disk architecture and those with the cloud disk architecture can provide genuinely authorized, stable, high-performance, and highly reliable database services, with only slight differences in performance, supported features, and other aspects. In terms of performance, Enhanced SSD cloud disks have the same performance as local disks. In terms of features, the cloud disk architecture supports more features, and more new features will be supported for this architecture in the future. In terms of storage, the cloud disk architecture supports a super large storage capacity.

ヘルプとサポート

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

フィードバック