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
ドキュメントTencentDB for SQL ServerGetting Started Creating TencentDB for SQL Server Instance

Creating TencentDB for SQL Server Instance

PDF
フォーカスモード
フォントサイズ
最終更新日: 2026-03-20 15:13:37

Overview

This document describes how to create an instance in the TencentDB for SQL Server console.

Prerequisites

You have registered a Tencent Cloud account and completed identity verification. For more information, see Signing Up and Identity Verification Guide.

Operation Steps

Creating an Instance

1. Go to the TencentDB for SQL Server purchase page, complete the configurations in Select a basic configuration, Set network and database, and
Confirm the configuration info. Then, read and indicate your consent to the Terms of Service, confirm that everything is correct, and click Buy Now. Step 1. Select a basic configuration In this step, you can set the basic configuration and specification options for the instance. The specific settings are as follows:
Basic Configuration
Billing Mode: Pay-as-you-go.
Region: We recommend that you choose the region closest to your end users to minimize access latency and improve download speed.
AZ: Select an AZ in the selected region. You can also use the AZ that is randomly allocated by the system.
Instance architecture: Support single-node, dual-node, and multi-node.
Storage Type:
When single-node architecture is selected, you can choose from premium cloud disk, SSD, balanced SSD, and enhanced SSD.
Note:
In Chinese mainland, if you need SSD for your basic edition instances, submit a ticket for application.
When two-node architecture is selected, you can choose from enhanced SSD, balanced SSD, and high-performance local SSD.
For multi-node architecture, available storage types include Enhanced SSD and Balanced SSD.
For a detailed description of each storage type and applicable scenarios, see Storage Types.
Database version: supports SQL Server 2008 R2, SQL Server 2012, SQL Server 2014, SQL Server 2016, SQL Server 2017 and SQL Server 2019 Enterprise and Standard version as well as SQL 2022 Enterprise version. The supported database versions vary by instance architecture. See the purchase page for details.
Disk encryption: For instances located in Shanghai, with storage type of Cloud Block Storage (CBS) and database version of SQL Server 2019/2022 Enterprise, the disk encryption feature can be used after applying for whitelisting. This feature is not supported in other regions or for other versions. If you need to use this feature, submit a ticket for application. The disk encryption field will only be displayed after you apply for disk encryption.
Key source: This item is displayed when disk encryption is enabled. Currently, the default key source is provided by Tencent Cloud.
Number of Replica Nodes: If multi-node architecture is selected, you need to specify the number of replica nodes from 2 to 5. The settings is not required for single-node or dual-node architectures.
Multi-AZ Deployment: This option is available when a dual-node or multi-node architecture is selected. For multi-node architecture, it can only be set to enabled.
Enabled: Multi-AZ Deployment is enabled, requiring the selection of secondary AZs in the next step. Each secondary node can be assigned a secondary AZ. Note: If all secondary nodes are deployed in the same AZ, the AZ-level disaster recovery is not supported. Please choose different secondary AZs.
Disabled: Multi-AZ Deployment is not enabled. Currently, only Shanghai, Beijing, Guangzhou, and Hong Kong (China) support multi-AZ deployment. Multi-AZ is a physical zone that combines multiple single AZs in the same region, which is used to protect databases in case of instance faults or AZ interruptions.
Replica AZ: If multi-AZ deployment is enabled, select the replica AZ based on the available resources.
Specs Configuration
Type: The Dedicated type is supported.
Filter: You can quickly filter the needed CPU and memory specifications for the instance. By default, all CPU and memory specifications are selected.
Selected instances: The specification information of the selected instances are displayed, including specification type and specification.
Instance Specifications: The detailed specification information is displayed, including the specification type, CPU, memory, maximum IOPS, supported AZs, and reference fees.
Storage Space: Select the required disk capacity.
Step 2. Set network and database
Network: VPC is supported. For connectivity testing, see Network Environment. Both VPCs and subnets support fuzzy search.
Note:
We recommend that you place the CVM and TencentDB instances under the same account in the same VPC in the same region.
A subnet is a logical network space in a VPC. You can create subnets in different AZs in the same VPC, which communicate with each other over the private network by default. Even if you select a subnet in another AZ in the same region, the network latency will not be increased because the actual business connection adopts nearby access.
Security Group: A security group is a stateful virtual firewall capable of filtering. As an important means for network security isolation provided by Tencent Cloud, it can be used to set network access controls for one or more TencentDB instances.
Note:
You can either create new security groups or choose from existing ones. You can also locate the target group by fuzzy search.
Instance Name: Select Set After Creation or Set Now.
System Time Zone: China Standard Time (Beijing Time) is supported by default.
For the purchase of the two-node local disk instances, submit a ticket to apply for the modification of the system time zone.
If you purchase a single-node, dual-node, or multi-node cloud disk instance, modification can be performed directly.
Sorting Rules of Character Set: The instance character set provides sorting rules for system data, namely, distinguishing between case-sensitive attributes and accent attributes. The Chinese_PRC_CI_AS is supported by default.
If a two-node local disk instance is purchased, submit a ticket to apply for the modification of the rules for the character set.
If you purchase a single-node, dual-node, or multi-node cloud disk instance, modification can be performed directly.
Project: TencentDB for SQL Server supports assigning instances to different projects for management. You can perform fuzzy search for projects by name.
Tag: You can use tags to easily categorize and manage resources. You are allowed to add multiple tags.
Maintenance Window/Maintenance Time: The backend system performs maintenance operations on your TencentDB for SQL Server instance from time to time to ensure its stability. To minimize the potential impact on your business, we recommend that you set an acceptable maintenance period for your business instance, usually during off-peak hours. You can select up to all the seven options for the maintenance windows.
Step 3. Confirm the configuration info
Display the configuration details of instances in step one and step two. If modifications are needed, click Edit. After all settings are confirmed, enable auto-renewal, read and agree to Terms of Service, and click Purchase Now.
Auto-renewal (for yearly/monthly subscription billing mode): If auto-renewal is enabled and the account balance is sufficient, the instance will be automatically renewed upon expiration based on the selected purchase duration: monthly or annually.
Purchase duration of 1 to 11 months: The auto-renewal period is one month, and the instance will be automatically renewed on a monthly basis upon expiration.
Purchase duration of 1 to 5 years: The auto-renewal period is one year, and the instance will be automatically renewed on a yearly basis upon expiration, with an auto-renewal discount applied.
After the purchase is completed, return to the Instance List and view the created instance. Once the status changes to Running, the instance is created successfully.

Creating an Account

1. In the Instance List, click an Instance ID or Manage in the Operation column to enter the instance management page.
2. On the instance management page, select Account Management > Create Account and enter relevant information in the pop-up window. After confirming that everything is correct, click OK.
Note:
The created account name and password will be used when connecting to TencentDB for SQL Server. Store them properly.

Creating a Database

1. In the Instance List, click an Instance ID or Manage in the Operation column to enter the instance management page.
2. On the Instance Management page, choose Database Management > Create Database, set configuration items in the pop-up window, confirm that everything is correct, and click OK.
Database Name: It can contain up to 32 letters, digits, and underscores and must start with a letter.
Character Set: Select the character set to be used by the database. Currently, most native character sets are supported.
Authorize Account: You can authorize existing accounts to access the database. If you haven't created an account yet, see Creating an account.
Remarks: Enter remarks of up to 256 characters.

Related APIs

API
Description
This API is used to create high-availability instances (local disk).
This API is used to create basic edition instances (cloud disk).
This API is used to create high-availability instances (cloud disk).
This API is used to query purchasable regions.
This API is used to query currently purchasable AZs.
This API is used to query purchasable specification configuration.
This API is used to query the status information on specifications, including the sales status and reference price. (The actual price is subject to the result returned by price querying APIs.)
This API is used to query the price of requested instances.
This API is used to query order information.
This API is used to query the instance ID by the order number.

ヘルプとサポート

この記事はお役に立ちましたか?

フィードバック