Data migration management
View Patent ↗Technologies are generally described for managing data migration between databases. In some examples, a data migration management system may include a data migration management unit configured to manage a migration of data stored in a first database to a second database, a game management unit configured to design a game for the migration of at least some of the data managed by the data migration management unit and to provide the designed game to a player, and a player management unit configured to manage participation of the player for the game designed by the game management unit.
1. A data migration management system, comprising:
a data migration management unit configured to:
identify a semantic difference between a first database and a second database,
classify data stored in the first database into a first portion of bulk data applicable to a bulk migration to the second database and a second portion of data necessitating semantic interpretation, suitable for a game, for a migration to the second database, and
design a migration application for the second portion of data based at least on the semantic difference between the first database and a second database, the semantic difference being associated with a compatibility between a data structure of the second portion of data and a data storage policy of the second database;
a game management unit configured to:
design the game to include a mission associated with the semantic difference between the first database and a second database for a migration of the second portion of data based on the migration application, and
provide the designed game for playing by a player; and
a player management unit configured to manage participation of the player for the game designed by the game management unit.
2. The data migration management system of claim 1 , further comprising:
a database management unit configured to manage the data stored in the first database.
3. The data migration management system of claim 1 , wherein the migration application is configured to resolve the semantic difference between the first database and the second database.
4. The data migration management system of claim 1 , wherein the migration application for the migration of the data is based at least in part on a designed migration process.
5. The data migration management system of claim 4 , wherein the data migration management unit is further configured to determine whether the designed application properly migrates the data stored in the first database to the second database.
6. The data migration management system of claim 1 , wherein the player management unit is further configured to manage registration of the player.
7. The data migration management system of claim 1 , wherein the player management unit is further configured to provide a predetermined award to the player when the player has successfully accomplished a mission of the game.
8. The data migration management system of claim 1 , wherein the player management unit is further configured to charge the player for the game.
9. The data migration management system of claim 1 , wherein the player management unit is further configured to design a market in which the player buys or sells the game and to manage the market.
10. The data migration management system of claim 1 , wherein the data storage policy of the second database is different from a data storage policy of the first database.
11. A method performed under control of a data migration management system, comprising:
identifying a semantic difference between a first database and a second database;
classifying data stored in the first database into a first portion of data and a second portion of data, the first portion of data being applicable to a bulk migration to the second database and the second portion of data necessitating semantic interpretation for a migration to the second database, wherein the necessitated semantic interpretation, suitable for a game, provides compatibility between the data stored in the first database and a data storage policy of the second database;
designing an application for migrating the second portion of data stored in the first database to the second database; and
designing the game to include a mission associated with the semantic difference between the first database and a second database based at least in part on the designed application.
12. The method of claim 11 , further comprising:
migrating the portion of data stored in the first database to the second database by playing the game.
13. The method of claim 11 , further comprising:
identifying the necessitated semantic interpretation between the first database and the second database; and
identifying, from the data stored in the first database, the second portion of data.
14. The method of claim 11 , further comprising:
requesting a player to play the game; and
revising the application based at least in part on a result of playing of the game by the player.
15. The method of claim 14 , further comprising:
validating whether the revised application properly migrates the data stored in the first database to the second database.
16. The method of claim 14 , further comprising:
revising the game based at least in part on the revised application.
17. The method of claim 14 , further comprising:
providing a predetermined award to the player when the player has successfully accomplished a mission of the game.
18. The method of claim 14 , further comprising:
charging the player for the game.
19. The method of claim 11 , further comprising:
requesting a player to play the game; and
generating another application based at least in part on a result of playing of the game by the player.
20. The method of claim 19 , further comprising:
generating another game based at least in part on the other application.
21. The method of claim 11 , further comprising:
providing a market in which the game is traded.
22. A non-transitory computer-readable storage medium having stored thereon computer-executable instructions that, in response to execution, cause a data migration management system to perform operations, comprising:
identifying a semantic difference between a first database and a second database;
classifying data stored in the first database into a first portion of data and a second portion of data, the first portion of data being applicable to a bulk migration to the second database and the second portion of data necessitating semantic interpretation for a migration to the second database, wherein the necessitated semantic interpretation, suitable for a game, provides compatibility between the data stored in the first database and a data storage policy of the second database; and
providing a player with the game designed to include a mission associated with the semantic difference between the first database and a second database to migrate the second portion of data to the second database for playing by a player.
23. The non-transitory computer-readable storage medium of claim 22 , wherein the operations further comprise:
migrating the second portion of data from the first database to the second database based at least in part on playing of the game by the player.
24. The non-transitory computer-readable storage medium of claim 22 , wherein the operations further comprise:
designing an application for the migration of the second portion of data to the second database; and
migrating the second portion of data from the first database to the second database based at least in part on the designed application.
25. The non-transitory computer-readable storage medium of claim 24 , wherein the operations further comprise:
designing the game based at least in part on the designed application.
26. The non-transitory computer-readable storage medium of claim 25 , wherein the operations further comprise:
revising the application based at least in part on a result of playing of the game by the player.