Category | Description |
Source/Target database type | 1. Source database type: Self-built databases (IDC self-built databases, self-built databases on CVM, and self-built databases on other vendors' clouds): SQL Server 2008 R2, 2012, 2014, 2016, 2017, 2019, and 2022. TencentDB for SQL Server (Tencent Cloud same-account and cross-account): SQL Server 2008 R2, 2012, 2014, 2016, 2017, 2019, and 2022. 2. Target database type: TencentDB for SQL Server (Tencent Cloud same-account and cross-account): SQL Server 2008 R2, 2012, 2014, 2016, 2017, 2019, and 2022. 3. Data migration using DTS is not currently supported in environments with network shared storage disks. |
Cross-Region Migration | Cross-region migration is supported. |
Migration Objects | 1. Only database-level migration is supported. This means that during migration, all objects within a database must be migrated together. Migration of individual tables is not supported. 2. The migration supports basic database and table objects. It does not support instance-level jobs, triggers, db links (link servers), or user permissions. These objects need to be recreated after migration. 3. Stored procedure migration is supported. |
Trigger type | Only migration, creation, and modification of the following triggers are supported. Other triggers are not supported for migration and will be automatically deleted after migration is completed.. CREATE_TABLE, ALTER_TABLE, DROP_TABLE CREATE_VIEW, ALTER_VIEW, DROP_VIEW CREATE_PROCEDURE, ALTER_PROCEDURE, DROP_PROCEDURE CREATE_FUNCTION, ALTER_FUNCTION, DROP_FUNCTION CREATE_INDEX, ALTER_INDEX, DROP_INDEX CREATE_STATISTICS, DROP_STATISTICS, UPDATE_STATISTICS CREATE_SYNONYM, DROP_SYNONYM CREATE_TYPE, DROP_TYPE DDL_TABLE_EVENTS, DDL_VIEW_EVENTS, and other DDL event groups Other non-security-sensitive DDL events |
Impact on the source database | When Data Transfer Service (DTS) is used to perform a full data migration, it occupies certain resources of the source instance, which may cause the source instance load to increase and add pressure to the database. If your database configuration is low, it is recommended to perform the migration during off-peak hours. |
Impact on the target database | After migration is completed, the database environment changes, and the new target database lacks cache and statistical information, which may cause database index invalidation and SQL performance degradation. If such a situation occurs, it is recommended to rebuild the index. |
Supported SQL statements | 1. DDL TABLE:CREATE TABLE,ALTER TABLE,DROP TABLE,TRUNCATE TABLE,RENAME TABLE VIEW:CREATE VIEW,ALTER VIEW,DROP VIEW INDEX:CREATE INDEX,DROP INDEX DATABASE:CREATE DATABASE,ALTER DATABASE,DROP DATABASE 2. DML INSERT,UPDATE,DELETE,REPLACE |
Operation restrictions | 1. Only one migration task can be initiated from the same source instance at a time. 2. During migration, do not modify or delete user information (including usernames, passwords, and permissions) and port numbers in the source and target databases. Otherwise, the migration task will fail. 3. During incremental synchronization, do not perform transaction log backups. Otherwise, the transaction logs will be truncated, resulting in a break in their continuity. 4. If you perform only a full data migration, do not write new data to the source instance during the migration. Otherwise, data inconsistency between the source and target will occur. For scenarios where data writing is required, to maintain data consistency in real time, it is recommended to choose full + incremental data migration. 5. For full + incremental data migration, do not write new data to the source database when you click Complete and the task status is Completing. It is recommended to stop writing for two minutes after clicking Complete. Otherwise, data inconsistency between the source and target databases may occur. 6. 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. |
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