Upgrading the Instance Version
Download
Modo Foco
Tamanho da Fonte
Attention:
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 initiate the configuration adjustment operation only when your TencentDB for SQL Server instance and its associated instances are in a normal state (Running) and no tasks are being executed.
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 | 2025 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.
When you perform operations such as cross-AZ migration / instance specification adjustment / instance edition upgrade that trigger a data migration scenario, system databases are not migrated. Do not create business-related data under system databases to avoid data loss after migration. Furthermore, under the aforementioned operation scenarios, non-standard system database operations and instance-level operations are not migrated together. You must handle them manually after the migration is completed.
Adjustment Impact
During the configuration adjustment process, the instance will undergo data migration. A larger data volume results in a longer data migration time. During this period, access to the instance is not affected.
A switch will be performed after migration is completed. During the switch, a second-level momentary database disconnection will occur. Ensure that your business application has a reconnection mechanism.
During the momentary disconnection, most operations related to databases, accounts, and networks cannot be performed. Ensure that you perform the switch operation during off-peak hours.
Fee Instructions
Upgrading the database version does not incur additional fees.
Operation Steps
1. Log in to the TencentDB for SQL Server console. Select the region where the instance is located, locate the corresponding instance in the instance list, and click More > Adjust Configuration in its 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 for the configuration change and select the orange prompt.
Within maintenance time: You can modify the maintenance time on the instance details page.
Adjust now: The configuration change will be executed 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. Return to the instance list. When the instance status changes from Adjusting instance configuration to Running, the version upgrade is complete. You can then query and confirm the new version of the instance on the Instance List or the Instance Details page.
Related APIs
API | Description |
This API is used to upgrade instances. |
Ajuda e Suporte
Esta página foi útil?
Você também pode entrar em contato com a Equipe de vendas ou Enviar um tíquete em caso de ajuda.
comentários