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

Restarting Instance

PDF
포커스 모드
폰트 크기
마지막 업데이트 시간: 2025-10-11 10:30:58
This document describes how to restart an instance in the console.

Scenario

Instance restart is a common maintenance method for TencentDB for SQL Server. It is similar to restarting a local database. You can choose to restart an instance during the maintenance period or restart it immediately according to your business needs.
Note:
Due to business security and risk control requirements, the system may prompt you to restart the instance in certain scenarios, such as cross-AZ migration and configuration adjustment, to lift corresponding feature limitations. At this point, follow the prompt in the console to complete the instance restart before you perform the corresponding operation.

Instructions for Sensitive Operations with MFA Integrated

To enhance the security of the cloud account, TencentDB for SQL Server supports MFA (Multi-Factor Authentication), which brings an extra layer of protection in addition to the username and password. After the MFA device verification is enabled, when you perform operations such as destroying instances/changing network/modifying IP addresses/resetting passwords/deleting accounts/resetting instances/performing primary-replica switch, a second identity verification based on the MFA dynamic code will be conducted. Such operations can be executed only after successful verification. For an introduction to MFA and how to enable the operation protection, see MFA Devices.

Limits

During the restart, the TencentDB for SQL Server instance cannot provide services. Therefore, make sure that an instance has stopped accepting business requests before restarting it. During the restart, if the business write volume is high, the restart may fail.
Restarting an instance does not change its physical attributes, so the private IP and any data stored in the instance will remain unchanged.
After the restart, reconnection to the database is needed. Make sure your business has a reconnection mechanism.
Restart the instance during off-peak hours to ensure success and minimize the impact on your business.

Directions

2. Select a region at the top, select one or multiple instances to be restarted, and click Restart at the top.

3. In the pop-up dialog box, set Time to Take Effect, select "I acknowledge the impact of instance restart", and click OK.

Immediate adjustment is selected by default. You can set Time to Take Effect as needed.
During maintenance time: Indicates that the current restart will only occur within the last maintenance period and will not restart multiple times according to the maintenance cycle. To modify the instance maintenance time, see Setting Instance Maintenance Information.
Adjust now: Indicates restarting the selected instance immediately.
4. Once the instance status changes from Restarting to Running, the restart is completed.

Related APIs

API
Description
This API is used to restart a database instance.

도움말 및 지원

문제 해결에 도움이 되었나요?

피드백