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

Upgrading Instance Version

PDF
포커스 모드
폰트 크기
마지막 업데이트 시간: 2025-12-03 11:31:12
Note:
This document contains important notes, and ignoring these notes may affect your business. Read it carefully.
TencentDB for SQL Server versions provided by Tencent Cloud follow the Major Version Lifecycle Description. To achieve better performance and security, you can adjust the configuration in the console and upgrade the instance to a later database version based on your actual needs. This document introduces how to upgrade the database version of the instance through the TencentDB for SQL Server console.

Supported versions

Version upgrade is supported for the single-node edition (formerly Basic Edition), two-node edition (formerly HA/Cluster Edition), and multi-node edition of TencentDB for SQL Server.

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.

Note

In TencentDB for SQL Server, the database compatibility level is a key setting that allows you to configure certain behaviors of the database to be compatible with specific versions of SQL Server. If your database is currently running stably at a lower compatibility level and your application does not require features that are only supported at higher compatibility levels, you can maintain the current compatibility level to preserve experiences of the existing business logic and features, avoiding the adaptation costs that may arise from changing the compatibility level and ensuring stable business operations. If existing applications need to use new features or new Transact-SQL versions, you can also upgrade the database compatibility level to the latest available version. For more details, see Microsoft Official Database (Transact-SQL) Compatibility Level.
Warning:
Discontinued features in specific SQL Server versions, which are removed from the SQL Server database engine, are not protected by the compatibility level.
Breaking changes in specific SQL Server versions (behavior changes between different database engine versions of SQL Server) may not be protected by the compatibility level. Though Transact-SQL behaviors are generally protected by the compatibility level, system objects that have been modified or removed are not protected by the compatibility level.
When the database version of an instance is upgraded, the compatibility level of the system database is upgraded automatically by default. For business databases (databases created through TencentDB for SQL Server), you can choose whether to automatically upgrade the database compatibility level to the latest version during the upgrade process and specify the specific time for the upgrade.
Before the upgrade, you can also see the Microsoft official documentation in the following table to assess discontinued features, breaking changes, and version feature changes that are not protected by the compatibility level. To ensure a smooth cross-version upgrade, it is recommended that you focus on intermediate version differences and prepare response measures in advance to ensure business continuity and stability.
Database Version
2012 Enterprise
2014 Enterprise
2016 Enterprise
2017 Enterprise
2019 Enterprise
2022 Enterprise
Microsoft official documentation
No discontinued features
No breaking changes
No discontinued features
No breaking changes
No breaking changes
After the database version is upgraded, rollback is not supported temporarily. It is recommended that you create a pay-as-you-go instance to test compatibility before the 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 a 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.

Fee Instructions

Upgrading the database version does not incur additional fees.

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 pop-up configuration adjustment window, select the database version to be changed, and choose whether to Upgrade the user database compatibility level to the latest automatically. After checking that the settings are correct, click OK.
Note:
Select the Time to Take Effect of the configuration adjustment and click the orange note.
During maintenance time: You can modify the maintenance time on the instance details page.
Adjust now: The configuration adjustment will be performed immediately.
Due to business security and risk control requirements, the system may prompt you to restart the instance to lift the feature limitations when you perform the version upgrade operation on instances. At this point, follow the prompt in the console to complete the instance restart before you perform the instance version upgrade operation.
If the option Upgrade the user database compatibility level to the latest automatically is set to Yes, the system will upgrade the database compatibility level automatically within the specified time period following the instance database version upgrade; if the option is set to No, the system will not upgrade the database compatibility level automatically.

3. For yearly/monthly subscription instances, confirm the configuration information and fees in the payment window after redirection, and click Submit Order. For pay-as-you-go instances, confirm the configuration information and fees in the payment window after redirection, and click Adjust.
4. You will be redirected to the instance list. When the instance status changes from Adjusting instance configuration to Running, the version upgrade is completed. You can query and check the new version on the Instance List or Instance Details page.

Related APIs

API
Description
This API is used to upgrade instances.

도움말 및 지원

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

피드백