CN106570086A - Data migration system and method - Google Patents
Data migration system and method Download PDFInfo
- Publication number
- CN106570086A CN106570086A CN201610911550.8A CN201610911550A CN106570086A CN 106570086 A CN106570086 A CN 106570086A CN 201610911550 A CN201610911550 A CN 201610911550A CN 106570086 A CN106570086 A CN 106570086A
- Authority
- CN
- China
- Prior art keywords
- data
- migration
- database
- migrated
- tables
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/25—Integrating or interfacing systems involving database management systems
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/22—Indexing; Data structures therefor; Storage structures
- G06F16/2228—Indexing structures
- G06F16/2255—Hash tables
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Databases & Information Systems (AREA)
- Data Mining & Analysis (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Software Systems (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention provides a data migration system and method. The data migration system comprises a source database, a target database, and a migration server, wherein a migration middle table is arranged in the source database; a migration middle library is arranged in a server where the target database is located; the source database divides data to be migrated into N batches of the data, and imports each batch of the data into the migration middle table in sequence; the migration server imports the data to be migrated in the migration middle table into a data table of the migration middle library, and detects whether the data to be migrated in the migration middle table is identical to the data to be migrated in the data table of the migration middle library or not; and if the data to be migrated in the migration middle table is identical to the data to be migrated in the data table of the migration middle library, the migration middle library imports each batch of the data in the data table of the migration middle library into the target database in sequence. The system and method provided by the invention has the advantages that according to user requirements, the large-volume data can be automatically divided into the small-volume data for multiple cyclic migrations during data migration, so that the sizes of log files in the databases can be effectively reduced, and the failure recovery time can be shortened.
Description
Technical field
The present invention relates to a kind of data mover system and data migration method.
Background technology
At present, based on SQL Server (Relational DBMS that Microsoft releases) data base, typically make
Data Migration Tools are Kettle (a ETL (data warehouse technology) instrument increased income) and SSIS (Microsoft SQL
Server Integration Services, generate high-performance data integrated solution) etc., it is also possible to use SQL
The data exporting instrument that Server is carried, these instruments have their own characteristics each, but there are problems that it is following some：
1) the small lot circulation migration of data cannot be carried out, whole data can only be disposably migrated, therefore causes data base
Journal file it is larger, if data base breaks down in data migration process, the database recovery time will be doubled and redoubled；
2) the difficult positioning of mistake, instrument can only spray less error information, and hardly possible navigates to the basic reason for causing to malfunction；
3) data are easy to lose, when tool abnormality interrupts, it is impossible to navigate to data record during interruption, lose when causing to interrupt
The data for migrating.
In sum, these problems increase many unstable factors to Data Migration.
The content of the invention
The technical problem to be solved in the present invention be in order to overcome prior art in can only disposably migrate whole data, and move
Move data defect easy to lose, there is provided a kind of data mover system and data migration method.
The present invention is to solve above-mentioned technical problem by following technical proposals：
A kind of data mover system, its feature is, the data mover system include source database, target database and
Migration server, is provided with migration middle table in the source database, in the server that the target database is located migration is provided with
Middle database；
The source database is used to for data to be migrated to split into N batch datas, and will successively be directed into per batch of data
In the migration middle table, the migration server is used to for the data to be migrated in the migration middle table to be directed into described moving
In moving the tables of data of middle database, it is additionally operable to detect the number of the data to be migrated in the migration middle table and the migration middle database
Whether the data to be migrated according to table are consistent, and if so, the migration middle database is used in the tables of data of the migration middle database
Every batch of data be directed into the target database successively.
It is preferred that being provided with migration step log in the migration server, the migration step log is used to record
Data to be migrated migrate each step to the target database from the source database.
In this programme, if in data migration process occur mistake, by check the migration step log come
Execution wrong step can be positioned at any time.
It is preferred that the migration server is additionally operable to before migrating data, the tables of data of the source database, described is detected
Whether the table structure of the tables of data of migration middle table, the tables of data of the migration middle database and the target database is consistent,
If so, migrating data is started, if it is not, synchronous meter structure.
It is preferred that the source database is additionally operable to after data to be migrated are all directed into the migration middle table, delete
Data to be migrated in the source database；
The migration middle database will be directed into successively after the target database per batch of data, and the migration middle table is also
Data to be migrated in for deleting the migration middle table, the migration middle database is additionally operable to delete the migration middle database
Data to be migrated in tables of data.
It is preferred that N is more than or equal to 100；And/or,
The source database and the target database are SQL Server data bases.
A kind of data migration method, its feature is that the data migration method utilizes data mover system described above
To realize, the data migration method is comprised the following steps：
S1, data to be migrated split into N batch datas, and institute will be successively directed into per batch of data by the source database
In stating migration middle table；
S2, the migration server data to be migrated in the migration middle table are directed into into the migration middle database
In tables of data；
S3, detect it is described migration middle table in data to be migrated with it is described migration middle database tables of data in it is to be migrated
Whether data are consistent, if so, execution step S4；
S4, it is described migration middle database by it is described migration middle database tables of data in every batch of data be directed into successively described in
Target database.
It is preferred that being provided with migration step log in the migration server, the migration step log is used to record
Data to be migrated migrate each step to the target database from the source database.
In this programme, if in data migration process occur mistake, by check the migration step log come
Execution wrong step can be positioned at any time.
It is preferred that in execution step S1Before, the data migration method also performs following steps：
S0, tables of data, the migration middle table, the tables of data of the migration middle database and the institute of detecting the source database
Whether the table structure for stating the tables of data of target database is consistent, if so, execution step S1, if it is not, synchronous meter structure.
It is preferred that in step S1In, after data to be migrated are all directed into the migration middle table, delete the source number
Data to be migrated according to storehouse；
In execution step S4Afterwards, the data migration method also performs following steps：
S5, delete it is described migration middle table in data to be migrated；
S6, delete it is described migration middle database tables of data in data to be migrated.
It is preferred that N is more than or equal to 100；And/or,
The source database and the target database are SQL Server data bases.
On the basis of common sense in the field is met, above-mentioned each optimum condition, can combination in any, obtain final product each preferable reality of the present invention
Example.
The present invention positive effect be：
Large batch of data can be split into small lot by the present invention automatically according to user's request, in data migration process
Data carry out repeatedly circulation migration, the log file size of data base can be effectively reduced, shorten failure recovery time.
When there is aborted in migration server, can be by checking migration step log, positioning performs mistake
Step, migrates the record of middle database and migration middle table when then checking failure, can position and problem data occur, so as to find
Cause the basic reason of mistake, while losing the situation of the data for migrating when can prevent from interrupting.
Description of the drawings
Fig. 1 is the structural representation of the data mover system of present pre-ferred embodiments.
Fig. 2 is the flow chart of the data migration method of present pre-ferred embodiments.
Specific embodiment
The present invention is further illustrated below by the mode of embodiment, but does not therefore limit the present invention to described reality
Among applying a scope.
As shown in figure 1, the present embodiment provides a kind of data mover system, the data mover system include source database 1,
Migration server 3 and target database 5, are provided with migration middle table 2, in the server that target database 5 is located in source database 1
Migration middle database 6 is provided with, migration step log 4 is provided with migration server 3, wherein, source database 1 and target database 5
SQL Server data bases are, in the present embodiment, source database 1 and target database 5 are respectively by the Internet and migration
Server 3 is communicated to connect, but is adjusted correspondingly also dependent on practical situation.
Before migrating data, migration server 3 is used to detect the tables of data of source database 1, migration middle table 2, migration
Whether the table structure of the tables of data of middle database 6 and the tables of data of target database 5 is consistent, if so, starts migrating data, if
It is no, synchronous meter structure.In the present embodiment, being designed as each table structure：The tables of data and source data of target database 5
The major key and row Type Length of the tables of data in storehouse 1 is consistent, but the tables of data of target database 5 is without self-propagation and default value；Migration
Middle table 2 is consistent with the row Type Length of the tables of data of source database 1, and migrating middle table 2 increases a special increasing certainly of migration
Long primary key column (comparing for the data after migration), adds a unique index consistent with the tables of data of source database 1；Migration
The tables of data of middle database 6 only difference is that the self-propagation attribute for removing row compared with migration middle table 2, retain its major key category
Property.
Source database 1 is used to for data to be migrated to split into N batch datas, and migration will be successively directed into per batch of data
In middle table 2.In the present embodiment, data to be migrated are 20000 datas, and 20000 datas are split into into 200 batch datas,
Therefore N is 200, each time an affairs are opened in circulation, and migrate batch of data, and often a collection of is 100 datas, each batch migration
After the completion of submit affairs to, such that it is able to be effectively reduced the log file size of data base, shorten failure recovery time.But,
The batch of fractionation is not limited to that quantity, can be carried out according to practical situations such as the operational capabilities of the demand of user and data base
Select.Source database 1 is additionally operable to after data to be migrated are all directed into migration middle table 2, deletes the tables of data of source database 1
In data to be migrated, so as to save memory space.
Migration server 3 is used to that the data to be migrated in migration middle table 2 to be directed into the tables of data of migration middle database 6
In, whether the data to be migrated in the data to be migrated being additionally operable in detection migration middle table 2 and the tables of data of migration middle database 6
Unanimously, if so, migrating middle database 6 is used to for the every batch of data in the tables of data of migration middle database 6 to be directed into number of targets successively
According to storehouse 5, migration middle database 6 will be directed into successively after target database 5 per batch of data, and migration middle table 2 is additionally operable to deletion and moves
The data to be migrated moved in middle table 2, migrate middle database 6 and are additionally operable to delete the number to be migrated in the tables of data of migration middle database 6
According to so as to complete data to be migrated from source database 1 to the migration of target database 5.Certainly can also migrate middle database 6 and move
Move the comparison of middle table 2 to complete, and after no data is lost, the data to be migrated in migration middle table 2 are deleted ahead of time, but in order to anti-
Only migrate the migrating data of middle database 6 and lose the situation of data to there is mistake during target database 5, or completed using migration
The mode of intermediate link data is deleted afterwards.Data to be migrated in the tables of data for deleting migration middle table 2 and migration middle database 6
Before, can carry out again target database 5 and migration middle database 6 between comparing, so as to ensure data without loss.
In whole transition process, migration step log 4 is migrated to mesh for recording data to be migrated from source database 1
Each step during mark data base 5, therefore when there is mistake, by checking migration step log 4 come Crestor at any time
Position performs wrong step.
The present embodiment also provides a kind of data migration method, and the data migration method utilizes Data Migration system described above
Unite to realize, the data migration method is comprised the following steps：
Step 101, the tables of data of detection source database, migration middle table, the tables of data of migration middle database and target data
Whether the table structure in storehouse is consistent, if so, execution step 102, if it is not, execution step 103.
In this step, being designed as each table structure：The tables of data of target database and the data of source database
The major key and row Type Length of table is consistent, but the tables of data of target database is without self-propagation and default value；Migration middle table and source
The row Type Length of the tables of data of data base is consistent, and migrating middle table increases a special self-propagation primary key column of migration, addition
One unique index consistent with the tables of data of source database；Migrate the tables of data of middle database compared with migration middle table, uniquely
Difference is the self-propagation attribute for removing row, retains its primary key attribute.
Data to be migrated are split into N batch datas by step 102, source database, and will be successively directed into per batch of data
In migration middle table, the data to be migrated in source database are deleted.
In this step, data to be migrated are 20000 datas, and 20000 datas are split into into 200 batch datas, therefore N is
200, each time an affairs are opened in circulation, and migrate batch of data, and often a collection of is 100 datas, and each batch migration is completed
After submit affairs to, such that it is able to be effectively reduced the log file size of data base, shorten failure recovery time.But, split
Batch be not limited to that quantity, can be selected according to practical situations such as the operational capabilities of the demand of user and data base
Select.Source database also after data to be migrated are all directed into migration middle table, are deleted treating in the tables of data of source database and is moved
Data are moved, so as to save memory space.
Return to step 101 after step 103, synchronous meter structure.
The table structure of synchronous four tables of data according to demand.
The data to be migrated migrated in middle table are directed into the tables of data of migration middle database for step 104, migration server
In.
Data to be migrated in step 105, detection migration middle table and the number to be migrated in the tables of data of migration middle database
It is consistent according to whether, if so, execution step 106, if it is not, execution step 107.
Every batch of data in the tables of data for migrating middle database is directed into successively number of targets by step 106, migration middle database
According to storehouse.
Return to step 105 after step 107, human intervention.
In whole transition process, migration step record table record data to be migrated are migrated to target data from source database
Each step during storehouse, therefore when there is mistake, can be positioned at any time by checking migration step log and perform mistake
By mistake the step of.Data to be migrated in migration middle table is detected and the data to be migrated in the tables of data of migration middle database are not
When consistent, migration step log is artificially checked, then check migration middle database and migrate the record of middle table, checking causes mistake
Basic reason, and correct mistake or again migrating data.
Step 108, the data to be migrated deleted in migration middle table.
Step 109, the data to be migrated deleted in the tables of data for migrating middle database.
Also can compare with migration middle table in migration middle database and complete, and after no data is lost, delete ahead of time in migration
Between data to be migrated in table, but lose number to there is mistake during target database to prevent from migrating middle database migrating data
According to situation, or using migration after the completion of delete intermediate link data by the way of.Deleting in the middle of migration middle table and migration
Before data to be migrated in the tables of data in storehouse, the data ratio between target database and migration middle database can be again carried out
It is right, so as to ensure data without loss.
In the present embodiment, according to user's request, in data migration process large batch of data can be split into automatically
The data of small lot carry out repeatedly circulation migration, can be effectively reduced the log file size of data base, shorten fault recovery
Time.
When there is aborted in migration server, can be by checking migration step log, positioning performs mistake
Step, migrates the record of middle database and migration middle table when then checking failure, can position and problem data occur, so as to find
Cause the basic reason of mistake, while losing the situation of the data for migrating when can prevent from interrupting.
Although the specific embodiment of the present invention is the foregoing described, it will be appreciated by those of skill in the art that this is only
It is to illustrate, protection scope of the present invention is defined by the appended claims.Those skilled in the art without departing substantially from
On the premise of the principle and essence of the present invention, various changes or modifications can be made to these embodiments, but these changes and
Modification each falls within protection scope of the present invention.
Claims (10)
1. a kind of data mover system, it is characterised in that the data mover system includes source database, target database and moves
Server is moved, migration middle table is provided with the source database, during migration is provided with the server that the target database is located
Between storehouse；
The source database is used to for data to be migrated to split into N batch datas, and will successively be directed into per batch of data described
In migration middle table, the migration server is used to that the data to be migrated in the migration middle table to be directed in the migration
Between storehouse tables of data in, the data to be migrated for being additionally operable to detect in the migration middle table and the tables of data of the migration middle database
In data to be migrated it is whether consistent, if so, the migration middle database be used for will be in the tables of data of the migration middle database it is every
Batch of data is directed into successively the target database.
2. data mover system as claimed in claim 1, it is characterised in that migration step note is provided with the migration server
Record table, the migration step log is migrated to the target database mistake for recording data to be migrated from the source database
Each step in journey.
3. data mover system as claimed in claim 1, it is characterised in that the migration server is additionally operable in migrating data
Before, detect tables of data, the migration middle table, the tables of data of the migration middle database and the number of targets of the source database
Whether the table structure according to the tables of data in storehouse is consistent, if so, starts migrating data, if it is not, synchronous meter structure.
4. data mover system as claimed in claim 1, it is characterised in that the source database is additionally operable in data to be migrated
After being all directed into the migration middle table, the data to be migrated in the source database are deleted；
The migration middle database will be directed into successively after the target database per batch of data, and the migration middle table is additionally operable to
The data to be migrated in the migration middle table are deleted, the migration middle database is additionally operable to delete the data of the migration middle database
Data to be migrated in table.
5. the data mover system as described in any one in Claims 1 to 4, it is characterised in that N is more than or equal to 100；
And/or,
The source database and the target database are SQL Server data bases.
6. a kind of data migration method, it is characterised in that the data migration method is moved using data as claimed in claim 1
Realizing, the data migration method is comprised the following steps shifting system：
S1, data to be migrated split into N batch datas, and described moving will be successively directed into per batch of data by the source database
In moving middle table；
S2, the migration server by it is described migration middle table in data to be migrated be directed into it is described migration middle database data
In table；
S3, detect it is described migration middle table in data to be migrated with it is described migration middle database tables of data in data to be migrated
It is whether consistent, if so, execution step S4；
S4, it is described migration middle database by it is described migration middle database tables of data in every batch of data be directed into the target successively
Data base.
7. data migration method as claimed in claim 6, it is characterised in that migration step note is provided with the migration server
Record table, the migration step log is migrated to the target database mistake for recording data to be migrated from the source database
Each step in journey.
8. data migration method as claimed in claim 6, it is characterised in that in execution step S1Before, the Data Migration side
Method also performs following steps：
S0, the tables of data, the migration middle table, the tables of data of the migration middle database and the mesh that detect the source database
Whether the table structure of the tables of data of mark data base is consistent, if so, execution step S1, if it is not, synchronous meter structure.
9. data migration method as claimed in claim 6, it is characterised in that in step S1In, all import in data to be migrated
To the migration middle table, the data to be migrated in the source database are deleted；
In execution step S4Afterwards, the data migration method also performs following steps：
S5, delete it is described migration middle table in data to be migrated；
S6, delete it is described migration middle database tables of data in data to be migrated.
10. the data migration method as described in any one in claim 6～9, it is characterised in that N is more than or equal to 100；
And/or,
The source database and the target database are SQL Server data bases.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610911550.8A CN106570086B (en) | 2016-10-19 | 2016-10-19 | Data migration system and data migration method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610911550.8A CN106570086B (en) | 2016-10-19 | 2016-10-19 | Data migration system and data migration method |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN106570086A true CN106570086A (en) | 2017-04-19 |
| CN106570086B CN106570086B (en) | 2020-08-14 |
Family
ID=58533919
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201610911550.8A Active CN106570086B (en) | 2016-10-19 | 2016-10-19 | Data migration system and data migration method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN106570086B (en) |
Cited By (18)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107203642A (en) * | 2017-06-19 | 2017-09-26 | 山东浪潮通软信息科技有限公司 | A kind of method of data synchronization and device |
| CN107422990A (en) * | 2017-07-28 | 2017-12-01 | 郑州云海信息技术有限公司 | A kind of dynamic migration method and device |
| CN107609068A (en) * | 2017-08-30 | 2018-01-19 | 苏州朗动网络科技有限公司 | A kind of noninductive moving method of data |
| CN108228102A (en) * | 2017-12-29 | 2018-06-29 | 北京奇虎科技有限公司 | Internodal data moving method, device, computing device and computer storage media |
| CN108304553A (en) * | 2018-02-01 | 2018-07-20 | 平安普惠企业管理有限公司 | Data migration method, device, computer equipment and storage medium |
| CN108536822A (en) * | 2018-04-09 | 2018-09-14 | 平安普惠企业管理有限公司 | Data migration method, device, system and storage medium |
| CN108897639A (en) * | 2018-06-05 | 2018-11-27 | Oppo广东移动通信有限公司 | Document handling method and device |
| CN108959611A (en) * | 2018-07-16 | 2018-12-07 | 中国联合网络通信集团有限公司 | Data cut-over method and device |
| CN108959545A (en) * | 2018-07-02 | 2018-12-07 | 山东汇贸电子口岸有限公司 | A kind of Oracle data processing method |
| CN109063005A (en) * | 2018-07-10 | 2018-12-21 | 阿里巴巴集团控股有限公司 | A kind of data migration method and system, storage medium, electronic equipment |
| CN109634635A (en) * | 2018-12-13 | 2019-04-16 | 中国银行股份有限公司 | A kind of data migration method and device |
| CN110347693A (en) * | 2019-07-11 | 2019-10-18 | 招商局金融科技有限公司 | Method of data synchronization, device and storage medium |
| CN111046016A (en) * | 2018-10-15 | 2020-04-21 | 珠海格力电器股份有限公司 | Data processing method, device and system and server |
| CN112148713A (en) * | 2020-09-29 | 2020-12-29 | 中国银行股份有限公司 | Data migration method and device between heterogeneous databases |
| US10922268B2 (en) | 2018-08-30 | 2021-02-16 | International Business Machines Corporation | Migrating data from a small extent pool to a large extent pool |
| CN112685384A (en) * | 2020-12-30 | 2021-04-20 | 平安普惠企业管理有限公司 | Data migration method and device, electronic equipment and storage medium |
| CN112749163A (en) * | 2020-12-30 | 2021-05-04 | 山东浪潮通软信息科技有限公司 | Data transmission method, device and medium |
| US11016691B2 (en) | 2019-01-25 | 2021-05-25 | International Business Machines Corporation | Migrating data from a large extent pool to a small extent pool |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103176988A (en) * | 2011-12-21 | 2013-06-26 | 上海博腾信息科技有限公司 | Data migration system based on software-as-a-service (SaaS) |
| CN103441988A (en) * | 2013-08-02 | 2013-12-11 | 广东电网公司电力科学研究院 | Data migration method crossing GIS platforms |
| WO2016138474A1 (en) * | 2015-02-26 | 2016-09-01 | Bittitan, Inc. | Data migration systems and methods including archive migration |
-
2016
- 2016-10-19 CN CN201610911550.8A patent/CN106570086B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103176988A (en) * | 2011-12-21 | 2013-06-26 | 上海博腾信息科技有限公司 | Data migration system based on software-as-a-service (SaaS) |
| CN103441988A (en) * | 2013-08-02 | 2013-12-11 | 广东电网公司电力科学研究院 | Data migration method crossing GIS platforms |
| WO2016138474A1 (en) * | 2015-02-26 | 2016-09-01 | Bittitan, Inc. | Data migration systems and methods including archive migration |
Cited By (28)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107203642A (en) * | 2017-06-19 | 2017-09-26 | 山东浪潮通软信息科技有限公司 | A kind of method of data synchronization and device |
| CN107422990B (en) * | 2017-07-28 | 2020-02-07 | 郑州云海信息技术有限公司 | Dynamic migration method and device |
| CN107422990A (en) * | 2017-07-28 | 2017-12-01 | 郑州云海信息技术有限公司 | A kind of dynamic migration method and device |
| CN107609068A (en) * | 2017-08-30 | 2018-01-19 | 苏州朗动网络科技有限公司 | A kind of noninductive moving method of data |
| CN108228102A (en) * | 2017-12-29 | 2018-06-29 | 北京奇虎科技有限公司 | Internodal data moving method, device, computing device and computer storage media |
| CN108228102B (en) * | 2017-12-29 | 2021-07-23 | 北京奇虎科技有限公司 | Method and device for data migration between nodes, computing equipment and computer storage medium |
| CN108304553A (en) * | 2018-02-01 | 2018-07-20 | 平安普惠企业管理有限公司 | Data migration method, device, computer equipment and storage medium |
| CN108536822A (en) * | 2018-04-09 | 2018-09-14 | 平安普惠企业管理有限公司 | Data migration method, device, system and storage medium |
| CN108897639B (en) * | 2018-06-05 | 2020-08-25 | Oppo广东移动通信有限公司 | File processing method and device |
| CN108897639A (en) * | 2018-06-05 | 2018-11-27 | Oppo广东移动通信有限公司 | Document handling method and device |
| CN108959545A (en) * | 2018-07-02 | 2018-12-07 | 山东汇贸电子口岸有限公司 | A kind of Oracle data processing method |
| CN109063005B (en) * | 2018-07-10 | 2021-05-25 | 创新先进技术有限公司 | Data migration method and system, storage medium and electronic device |
| CN109063005A (en) * | 2018-07-10 | 2018-12-21 | 阿里巴巴集团控股有限公司 | A kind of data migration method and system, storage medium, electronic equipment |
| CN108959611A (en) * | 2018-07-16 | 2018-12-07 | 中国联合网络通信集团有限公司 | Data cut-over method and device |
| US10922268B2 (en) | 2018-08-30 | 2021-02-16 | International Business Machines Corporation | Migrating data from a small extent pool to a large extent pool |
| CN111046016A (en) * | 2018-10-15 | 2020-04-21 | 珠海格力电器股份有限公司 | Data processing method, device and system and server |
| CN109634635A (en) * | 2018-12-13 | 2019-04-16 | 中国银行股份有限公司 | A kind of data migration method and device |
| CN109634635B (en) * | 2018-12-13 | 2023-02-21 | 中国银行股份有限公司 | Data migration method and device |
| US11016691B2 (en) | 2019-01-25 | 2021-05-25 | International Business Machines Corporation | Migrating data from a large extent pool to a small extent pool |
| US11442649B2 (en) | 2019-01-25 | 2022-09-13 | International Business Machines Corporation | Migrating data from a large extent pool to a small extent pool |
| US11531486B2 (en) | 2019-01-25 | 2022-12-20 | International Business Machines Corporation | Migrating data from a large extent pool to a small extent pool |
| US11714567B2 (en) | 2019-01-25 | 2023-08-01 | International Business Machines Corporation | Migrating data from a large extent pool to a small extent pool |
| CN110347693A (en) * | 2019-07-11 | 2019-10-18 | 招商局金融科技有限公司 | Method of data synchronization, device and storage medium |
| CN112148713A (en) * | 2020-09-29 | 2020-12-29 | 中国银行股份有限公司 | Data migration method and device between heterogeneous databases |
| CN112148713B (en) * | 2020-09-29 | 2024-04-16 | 中国银行股份有限公司 | Method and device for data migration between heterogeneous databases |
| CN112685384A (en) * | 2020-12-30 | 2021-04-20 | 平安普惠企业管理有限公司 | Data migration method and device, electronic equipment and storage medium |
| CN112749163A (en) * | 2020-12-30 | 2021-05-04 | 山东浪潮通软信息科技有限公司 | Data transmission method, device and medium |
| CN112749163B (en) * | 2020-12-30 | 2023-08-01 | 浪潮通用软件有限公司 | Data transmission method, device and medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN106570086B (en) | 2020-08-14 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN106570086A (en) | Data migration system and method | |
| Deng et al. | The Data Civilizer System. | |
| US9336263B2 (en) | Data loading systems and methods | |
| Li | Transforming relational database into HBase: A case study | |
| US10311048B2 (en) | Full and partial materialization of data from an in-memory array to an on-disk page structure | |
| Gonzalez et al. | Google fusion tables: data management, integration and collaboration in the cloud | |
| US10180992B2 (en) | Atomic updating of graph database index structures | |
| US7890466B2 (en) | Techniques for increasing the usefulness of transaction logs | |
| Abouzied et al. | Invisible loading: access-driven data transfer from raw files into database systems | |
| US9639542B2 (en) | Dynamic mapping of extensible datasets to relational database schemas | |
| CN108694195B (en) | Management method and system of distributed data warehouse | |
| CN107408114B (en) | Identifying join relationships based on transactional access patterns | |
| US10628492B2 (en) | Distributed graph database writes | |
| CN110799960A (en) | System and method for database tenant migration | |
| US6289355B1 (en) | Fast log apply | |
| US20130151476A1 (en) | Processing archive content based on hierarchical classification levels | |
| US20170255708A1 (en) | Index structures for graph databases | |
| EP3120261A1 (en) | Dependency-aware transaction batching for data replication | |
| US11269954B2 (en) | Data searching method of database, apparatus and computer program for the same | |
| WO2018097846A1 (en) | Edge store designs for graph databases | |
| CN108334596B (en) | Massive relational data efficient parallel migration method for big data platform | |
| US10489356B1 (en) | Truncate and append database operation | |
| US20190286622A1 (en) | Deleting rows from tables in a database without an index | |
| CN106970929A (en) | Data lead-in method and device | |
| Kvet et al. | The complexity of the data retrieval process using the proposed index extension |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |