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

Migrating Data from CVM-based SQL Server Instance

PDF
フォーカスモード
フォントサイズ
最終更新日: 2025-09-12 14:27:16

Operation Scenarios

TencentDB for SQL Server supports migrating data from a CVM-based self-created SQL Server database to a TencentDB for SQL Server instance. This document describes how to configure and run such a migration task.
Note:
Before migration, please make sure that the SQL Server version of the target instance is not below that of the source instance.
Support the upload of single bak file and tar compressed file for recovery.
The name of the migrated database cannot be the same as that of the TencentDB for SQL Server instance.
The data migration function of the legacy version has been taken offline, and this document is for the reference of existing users only. To use the new data migration feature, see Data Migration Solution Overview.

Directions

Step 1. Create a migration task

1. Log in to the TencentDB for SQL Server Console and select Data Migration (Legacy) on the left sidebar.
2. Click Create Task, enter the task name, source database information, and target database information, and select CVM-based self-created SQL Server database as the source instance type.

3. After clicking Next, you need to configure the source SQL Server instance first and then configure the migration task.
Note:
If the error message "Source instance info checking failed!" is displayed, please check the following items for troubleshooting:
Whether the sa account of the source SQL Server instance exists.
Whether the sa account password of the source SQL Server instance is correct.
Whether the IP and port connectivity of the source SQL Server instance work properly.

Step 2. Configure the source SQL Server instance

1. Enable the sa account for the source SQL Server instance.
2. Select Allow remote connections to this server in Connections and set a reasonable remote query timeout period.
3. Select SQL Server and Windows authentication mode in Security.
4. Enable TCP/IP.
5. Enable the built-in account and select localsystem.
6. Allow SQL Server port communication and open port 445 (for the basic network) or 49001 (for a VPC) in Windows Firewall.
7. (Optional) If VPC is selected as the CVM Network, you need to configure the freeSSHd tool.
8. Download and install freeSSHd with the default options and agree to start the freeSSHd service.
9. Double-click the freeSSHd icon on the desktop. Then, right-click the freeSSHd icon in the taskbar to open the Settings page for configuration.
10. Select the SSH tab and set the port to 49001 (the default port here is 22, which should be changed to 49001).


11. Select the Server status tab and start the SSH server.
12. Select the Authentication tab and select Allowed for password authentication.
13. Select the Users tab and enter the user tencent_vpc_migrate (this username cannot be changed) and the password tencent_vpc_migrate (this password cannot be changed) as shown below:


14. Use D:\\dbbackup\\ (this path cannot be changed) as the backup folder used during SQL Server migration. Select the SFTP tab and configure this path as the "SFTP home path".

Step 3. Configure the migration task

Select the migration type, set the database (by selecting the databases/tables to be migrated), and click Save and Verify. If the verification fails, you can troubleshoot as prompted.

Step 4. Start the migration task

After the task is created, return to the task list. At this point, the task status is Initializing. Select the task and click Start to sync the task.

Step 5. Complete the migration task

After the data synchronization is completed (i.e., the progress bar shows 100%), you need to click Complete to end the synchronization process. If you selected Incremental Synchronization when configuring the migration task, you need to click Complete when the progress bar shows 99%. You can check whether the migration is successful on the Status.
If the task status is task successful, the data migration is successful.
If the status is task failed, the data migration failed. Please check the failure information, fix it accordingly, and then migrate again.

Related APIs

API
Description
This API is used to create a migration task.
This API is used to modify an existing migration task.
This API is used to start a pre-migration verification task, applicable to the migration method where the migration source type is TencentDB for SQL Server.
This API is used to start running a migration task.
This API is used to terminate a migration task.
This API is used to complete a migration task.
This API is used to delete a migration task.
This API is used to query migration task details.
This API is used to query the list of eligible migration tasks based on the entered criteria.
This API is used to query the list of databases to be migrated.
This API is used to query the progress of the migration verification task, inquiry of migration check task progress, applicable to the migration method where the migration source type is TencentDB for SQL Server.

ヘルプとサポート

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

フィードバック