Compute
Elastic Cloud Server
Huawei Cloud Flexus
Bare Metal Server
Auto Scaling
Image Management Service
Dedicated Host
FunctionGraph
Cloud Phone Host
Huawei Cloud EulerOS
Networking
Virtual Private Cloud
Elastic IP
Elastic Load Balance
NAT Gateway
Direct Connect
Virtual Private Network
VPC Endpoint
Cloud Connect
Enterprise Router
Enterprise Switch
Global Accelerator
Management & Governance
Cloud Eye
Identity and Access Management
Cloud Trace Service
Resource Formation Service
Tag Management Service
Log Tank Service
Config
OneAccess
Resource Access Manager
Simple Message Notification
Application Performance Management
Application Operations Management
Organizations
Optimization Advisor
IAM Identity Center
Cloud Operations Center
Resource Governance Center
Migration
Server Migration Service
Object Storage Migration Service
Cloud Data Migration
Migration Center
Cloud Ecosystem
KooGallery
Partner Center
User Support
My Account
Billing Center
Cost Center
Resource Center
Enterprise Management
Service Tickets
HUAWEI CLOUD (International) FAQs
ICP Filing
Support Plans
My Credentials
Customer Operation Capabilities
Partner Support Plans
Professional Services
Analytics
MapReduce Service
Data Lake Insight
CloudTable Service
Cloud Search Service
Data Lake Visualization
Data Ingestion Service
GaussDB(DWS)
DataArts Studio
Data Lake Factory
DataArts Lake Formation
IoT
IoT Device Access
Others
Product Pricing Details
System Permissions
Console Quick Start
Common FAQs
Instructions for Associating with a HUAWEI CLOUD Partner
Message Center
Security & Compliance
Security Technologies and Applications
Web Application Firewall
Host Security Service
Cloud Firewall
SecMaster
Anti-DDoS Service
Data Encryption Workshop
Database Security Service
Cloud Bastion Host
Data Security Center
Cloud Certificate Manager
Edge Security
Situation Awareness
Managed Threat Detection
Blockchain
Blockchain Service
Web3 Node Engine Service
Media Services
Media Processing Center
Video On Demand
Live
SparkRTC
MetaStudio
Storage
Object Storage Service
Elastic Volume Service
Cloud Backup and Recovery
Storage Disaster Recovery Service
Scalable File Service Turbo
Scalable File Service
Volume Backup Service
Cloud Server Backup Service
Data Express Service
Dedicated Distributed Storage Service
Containers
Cloud Container Engine
SoftWare Repository for Container
Application Service Mesh
Ubiquitous Cloud Native Service
Cloud Container Instance
Databases
Relational Database Service
Document Database Service
Data Admin Service
Data Replication Service
GeminiDB
GaussDB
Distributed Database Middleware
Database and Application Migration UGO
TaurusDB
Middleware
Distributed Cache Service
API Gateway
Distributed Message Service for Kafka
Distributed Message Service for RabbitMQ
Distributed Message Service for RocketMQ
Cloud Service Engine
Multi-Site High Availability Service
EventGrid
Dedicated Cloud
Dedicated Computing Cluster
Business Applications
Workspace
ROMA Connect
Message & SMS
Domain Name Service
Edge Data Center Management
Meeting
AI
Face Recognition Service
Graph Engine Service
Content Moderation
Image Recognition
Optical Character Recognition
ModelArts
ImageSearch
Conversational Bot Service
Speech Interaction Service
Huawei HiLens
Video Intelligent Analysis Service
Developer Tools
SDK Developer Guide
API Request Signing Guide
Terraform
Koo Command Line Interface
Content Delivery & Edge Computing
Content Delivery Network
Intelligent EdgeFabric
CloudPond
Intelligent EdgeCloud
Solutions
SAP Cloud
High Performance Computing
Developer Services
ServiceStage
CodeArts
CodeArts PerfTest
CodeArts Req
CodeArts Pipeline
CodeArts Build
CodeArts Deploy
CodeArts Artifact
CodeArts TestPlan
CodeArts Check
CodeArts Repo
Cloud Application Engine
MacroVerse aPaaS
KooMessage
KooPhone
KooDrive
On this page

RDS for SQL Server Product Series

Updated on 2024-09-12 GMT+08:00
RDS for SQL Server DB instances are classified into the following types:
  • Single
  • Primary/Standby
  • Cluster
Table 1 DB instance types

DB Instance Type

Description

Notes

Scenarios

Single

A single-node architecture is more cost-effective than a primary/standby DB pair.

If a fault occurs on a single instance, the instance cannot recover in a timely manner.

  • Personal learning
  • Microsites
  • Development and testing environment of small- and medium-sized enterprises

Primary/Standby

An HA architecture. A pair of primary and standby DB instances shares the same IP address and can be deployed in different AZs.

  • When a primary instance is being created, a standby instance is provisioned synchronously to provide data redundancy. The standby instance is invisible to you after being created.
  • If the primary instance fails, a failover occurs, during which database connection is interrupted. If there is a replication delay between the primary and standby instances, the failover takes an extended period of time. The client needs to be able to reconnect to the instance.
  • Production databases of large and medium enterprises
  • Applications for the Internet, Internet of Things (IoT), retail e-commerce sales, logistics, gaming, and other industries

Cluster

The Microsoft Always On architecture. There is one primary node, one standby node, and up to five read-only nodes. It features higher availability, reliability, and scalability.

Only for RDS for SQL Server.

  • Finance industry
  • Internet industry
  • Hotel industry
  • Online education

Advantage Comparison

  • Single DB instances: support the creation of read replicas and support the queries of error logs and slow query logs. Different from primary/standby DB instances that have two database nodes, a single DB instance has only one node, reducing the price to half of primary/standby DB instances. If the node fails, the restoration will take a long time. Therefore, single DB instances are not recommended for sensitive services that have high requirements on database availability.
  • Primary/Standby DB instances: use the standby database node only for failover and restoration. The standby database node does not provide services. The performance of single DB instances is similar to or even higher than primary/standby DB instances because standby nodes cause extra performance overhead.
  • Cluster instances: use the Microsoft Always On architecture with one primary node, one standby node, and up to five read-only nodes. It features higher availability, reliability, and scalability.
Table 2 Function comparisons

Function

Single

Primary/Standby

Cluster

Number of nodes

1

2

2

Specifications

vCPUs: a maximum of 64

Memory: a maximum of 512 GB

Storage: a maximum of 4,000 GB

vCPUs: a maximum of 64

Memory: a maximum of 512 GB

Storage: a maximum of 4,000 GB

vCPUs: a maximum of 64

Memory: a maximum of 512 GB

Storage: a maximum of 4 TB

Monitoring and alarms

Supported

Supported

Supported

Security group

Supported

Supported

Supported

Backup and restoration

Supported

Supported

Supported

Recycle bin

Supported

Supported

Supported

Parameter settings

Supported

Supported

Supported

SSL

Supported

Supported

Supported

Log management

Supported

Supported

Supported

Read replicas (which need to be created)

Not supported

Not supported

Supported

High-frequency monitoring

Supported

Supported

Supported

Failover

Not supported

Supported

Supported

Standby DB instance migration

Not supported

Supported

Supported

Manual primary/standby switchover

Not supported

Supported

Supported

Instance class change

Supported

Supported

Supported

We use cookies to improve our site and your experience. By continuing to browse our site you accept our cookie policy. Find out more

Feedback

Feedback

Feedback

0/500

Selected Content

Submit selected content with the feedback