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
DocumentationTencentDB for SQL ServerOperation GuideData Migration (New)Using DTS to Migrate DataPre-Validation Failure HandlingMigration Parameter Check

Migration Parameter Check

PDF
Focus Mode
Font Size
Last updated: 2024-12-24 15:00:34

Check details

The target instance must not contain any databases to be migrated; otherwise, an error will occur with the details: "The database to be migrated already exists in the target instance."
The provided migration account must be able to log in normally; otherwise, an error will occur with the details: "The provided migration account cannot log in."
The name of the database to be migrated must not contain sensitive characters; otherwise, an error will occur with the details: "The name of the database to be migrated contains sensitive characters."
The database to be migrated must adhere to specific standards and cannot contain the keywords master, model, msdb, tempdb, monitor, Master, Model, Msdb, Tempdb, Monitor. Failure to comply will result in an error, with the detailed message stating: "The database to be migrated does not meet the required standards."
The migrated database name must be at least 1 character long, otherwise an error will occur. Error details: "The migrated database name must be at least 1 character long."
The migrated database name cannot exceed 64 characters, otherwise an error will occur. Error details: "The migrated database name cannot exceed 64 characters."

Fix

Serial number
Error details
Fix
1
The migrated database already exists in the target instance
Please change the database to be migrated in the source instance or delete the database with the same name as the migrated database in the target instance.
2
The provided migration account cannot log in to
1. Please check if the source instance is already in Running Status.
2. Please check if the port of the source instance is being blocked by the Firewall Security Group.
3. Please check if the port of the source instance is entered incorrectly.
4. Please check if the account and password of the source instance are entered incorrectly.
3
The name of the database to be migrated contains sensitive characters
Please change the database to be migrated in the source instance or rename the database to remove illegal characters before migration.
4
The database to be migrated does not meet the required standards
Please replace the database being migrated in the source instance, or modify the relevant keywords associated with the database being migrated in the source instance, before proceeding with the migration.
5
The migrated database name must be at least 1 character long
Please change the database to be migrated in the source instance or rename the database according to naming standards before migration.
6
The migrated database name must be no longer than 64 characters
Please change the database to be migrated in the source instance or rename the database according to naming standards before migration.
Previous Topic: Cloud Database Across-Account Migration GuideNext Topic: Migration Network Check

Help and Support

Was this page helpful?

Help us improve! Rate your documentation experience in 5 mins.

Feedback