Release Notes
Announcements
Category | Description |
Source/Target Type | 1. Source Type: Self-built databases (IDC self-built and CVM self-built) SQL Server 2008R2, 2012, 2014, 2016, 2017, 2019, and 2022. TencentDB (intra-account and cross-account) for SQL Server 2008R2, 2012, 2014, 2016, 2017, 2019, and 2022. 2. Target Type: TencentDB (intra-account and cross-account) for SQL Server 2008R2, 2012, 2014, 2016, 2017, 2019, and 2022. 3. Data Transfer Service (DTS) migration is not supported in network shared storage disk environments. |
Cross-region Migration | Currently, cross-region migration is supported in the Chinese Mainland and Hong Kong (China) regions. Other regions do not support cross-region migration. |
Migration Object | 1. Only database-level migration is supported, that is, all objects in the database must be migrated together. Single-table migration is not supported. 2. The migration of basic database and table objects is supported, but migration of instance-level jobs, triggers, DB links (link servers), or user permissions is not supported.These objects need to be rebuilt after the migration is complete.. |
Source Database Impact | 1. During full data migration, DTS consumes certain source instance resources, which may increase the load and pressure of the source database. If your database configuration is low, we recommend you perform the migration during off-peak hours. 2. The full data migration process is implemented through locked migration, and write operations will be briefly (in seconds) blocked during table locking. 3. Due to changes in the physical environment of data files after migration, database indexes will become invalid. You need to rebuild the indexes after migration; otherwise, database performance may significantly decline. 4. By default, a lock-free synchronization method is used. In the full data export stage, a global lock (FTWRL) will not be applied on the source database; only table locks are applied on tables without a primary key. |
Supported SQL Statements | 1. DDL TABLE: CREATE TABLE, ALTER TABLE, DROP TABLE, TRUNCATE TABLE, and RENAEM TABLE VIEW: CREATE VIEW, A LTER VIEW, and DROP VIEW INDEX: CREATE INDEX, and DROP INDEX DATABASE: CREATE DATABASE, ALTER DATABASE, and DROP DATABASE 2. DML INSERT, UPDATE, DELETE, and REPLACE |
Limits on Operations | 1. Only one migration task can be initiated at any time for the same source instance. 2. Do not modify or delete user information (including username, password, and permissions) in the source and target databases and port numbers during migration; otherwise, the migration task will fail. 3. Do not perform transaction log backup during incremental sync; otherwise, the transaction log will be truncated and become discontinuous. 4. If you only perform full data migration, do not write new data into the source database during migration; otherwise, the data in the source and target databases will be inconsistent. In scenarios with data writes, to ensure data consistency in real time, we recommend that you select full + incremental data migration. 5. For full + incremental data migration, when the task status is completing after clicking Complete, do not write new data into the source database. We recommend stopping data writes for two minutes after clicking Complete; otherwise, the data in the source and target databases may be inconsistent. |
フィードバック