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
DocumentationTencentDB for SQL Server

Adjusting Instance Architecture

Focus Mode
Font Size
Last updated: 2024-01-18 17:20:33
This document describes how to adjust the instance architecture in the TencentDB for SQL Server console.

Architecture background

TencentDB for SQL Server supports the following architectures:
Type
Description
Single-node (formerly Basic Edition)
(1) It is deployed on a single node and based on premium cloud disks, with computing and storage separated.
(2) It offers extremely high cost-effectiveness.
Two-node (formerly High Availability/Cluster Edition)
2008 R2/2012/2014/2016 Enterprise
(1) It consists of one primary database and one mirror database deployed across racks/AZs.
(2) Each database corresponds to a monitoring agent that monitors the database through heartbeat in real time.
Two-node (formerly High Availability/Cluster Edition)
2017/2019 Enterprise
(1) It adopts the Always On cluster deployment architecture, including one primary and one replica deployed across racks/AZs by default.
(2) Each database corresponds to a monitoring agent that monitors the database through heartbeat in real time.
For detailed descriptions, see Product Architecture.

Prerequisites

You can adjust the configuration of a TencentDB for SQL Server instance and its associated instances only when they are in running status and are not executing any tasks.

Notes

Currently, the architecture cannot be downgraded back after an upgrade.

Impact of configuration adjustment

Data migration will be involved during the instance configuration adjustment, and the larger the data volume, the longer the data migration time. Access to the instance will not be affected during this period.
A switch will be performed after migration is completed, which causes a momentary disconnection from the database for few seconds. Make sure that your business has a reconnection mechanism.
Most database, account, and network operations are unavailable during the momentary disconnection. Therefore, we recommend that you perform the switch during off-peak hours.

Directions

1. Log in to the TencentDB for SQL Server console, select the region and target instance in the instance list, and click Adjust Configuration in the Operation column.


2. In the Adjust Configuration window that pops up, select the desired architecture and click Confirm.
Note:
If data migration is involved during the change, you need to select the effective time and click the orange note; otherwise, you don't need to select the effective time.
During maintenance time: You can modify the maintenance time on the instance details page.
Adjust now: The configuration adjustment will be performed immediately.

3. You will be redirected to the instance list. When the instance status changes from Switching (after configuration adjustment) to Running, the architecture upgrade is completed. You can query and check the new architecture on the Instance List or Instance Details page.

Help and Support

Was this page helpful?

Help us improve! Rate your documentation experience in 5 mins.

Feedback