CN101751429A - Method and device for synchronizing foreground database and background database - Google Patents
Method and device for synchronizing foreground database and background database Download PDFInfo
- Publication number
- CN101751429A CN101751429A CN200810239529A CN200810239529A CN101751429A CN 101751429 A CN101751429 A CN 101751429A CN 200810239529 A CN200810239529 A CN 200810239529A CN 200810239529 A CN200810239529 A CN 200810239529A CN 101751429 A CN101751429 A CN 101751429A
- Authority
- CN
- China
- Prior art keywords
- subtask
- grouping
- foreground
- groups
- flow process
- 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.)
- Pending
Links
Images
Landscapes
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention discloses a method for synchronizing a foreground database and a background database, which comprises the following steps: acquiring the preset task definition for synchronizing the foreground database and the background database, and dividing the preset task definition into a plurality of subtasks; grouping the subtasks, wherein each group contains at least one subtask; and executing the subtasks in all groups, wherein the subtasks in all groups are executed concurrently. Thus, compared with the serial execution mode for the subtasks in the prior art, the concurrent execution mode of the subtasks in different groups enables the subtasks in the groups to be mutually independent, thereby reducing the dependence among the subtasks and shortening the time for executing the subtasks to some extent; and thus, the invention effectively enhances the efficiency of synchronizing the foreground database and the background database. The invention also discloses a server.
Description
Technical field
The present invention relates to computer realm, particularly a kind of method for synchronous of foreground and background databases and device.
Background technology
Along with development of computer, the user is more and more higher to the requirement of data storage administration, and correspondingly, various data storage services are also arisen at the historic moment.Wherein, the oracle database technology is one of data storage management technology that is widely used.The isomery service of oracle database technology is big characteristics of this technology, so-called isomery service is meant, there are two databases, one is the Foreground Data storehouse, be used for the real-time collecting user related data, one is background data base, is used for the user related data of collecting is put in order planning and preservation.The data that Foreground Data storehouse and background data base are preserved will regularly be carried out synchronously, to be consistent.
But under the prior art, Foreground Data storehouse and background data base carry out synchronous flow process and have following problem:
1, in the synchronous flow process of foreground and background databases, there is not independent carrying out of task, all tasks are all carried out according to the order serial of setting, be that each task all need just begin to start after its previous task is finished, like this, once mistake appears in certain task, so, the synchronous flow process of whole foreground and background databases just can stop, after needing manually it to be safeguarded, start anew again again to carry out, obviously, this has seriously reduced the execution efficient of the synchronous flow process of foreground and background databases, has reduced user experience on the degree having very much.
2, the execution of the synchronous flow process of whole foreground and background databases need be read the sql statement of people's exploitation, like this, causes the synchronous flow process of foreground and background databases to go wrong because of artificial mistake easily.
Summary of the invention
The embodiment of the invention provides a kind of method for synchronous of foreground and background databases, in order to improve the execution efficient of the synchronous flow process of foreground and background databases.
The concrete technical scheme that the embodiment of the invention provides is as follows:
A kind of method of synchronous foreground and background databases comprises:
Obtain defaultly in order to finishing the synchronous task definition of foreground and background databases, and the task definition that will preset is divided into the plurality of sub task;
The plurality of sub task is divided into groups, comprise at least one subtask in every group;
Carry out the subtask in each grouping; Wherein, each tasks in parallel of dividing into groups is carried out.
A kind of server comprises:
Storage unit is used to preserve default task definition;
Determining unit is used to obtain default in order to finishing the synchronous task definition of foreground and background databases, and the task definition that will preset is divided into the plurality of sub task;
Grouped element is used for the plurality of sub task is divided into groups, and comprises at least one subtask in every group;
Performance element, the subtask that is used for carrying out each grouping; Wherein, each tasks in parallel of dividing into groups is carried out.
In the embodiment of the invention, when carrying out the synchronous flow process of foreground and background databases, server obtains default in order to finishing the synchronous task definition of foreground and background databases earlier, and the task definition that will preset is divided into the plurality of sub task; Again the plurality of sub task is divided into groups, comprise at least one subtask in every group; Then, the subtask in each grouping of execution; Wherein, each tasks in parallel of dividing into groups is carried out.Like this, mode with respect to each subtask serial execution under the prior art, in the embodiment of the invention, the mode that belongs to executed in parallel between the subtask of different grouping makes that the subtask in each grouping is separate, thereby reduced the dependence between the subtask, shorten the required time of subtasking to a certain extent, and then improved the efficient of the synchronous flow process of foreground and background databases effectively.
Description of drawings
Figure 1A is a system architecture synoptic diagram in the embodiment of the invention;
Figure 1B is a server capability structural representation in the embodiment of the invention;
Fig. 2 is the synchronous process flow diagram of foreground and background databases in the embodiment of the invention;
Fig. 3 is a grouping synoptic diagram in subtask in the embodiment of the invention.
Embodiment
In order to improve the execution efficient of the synchronous flow process of foreground and background databases, in the embodiment of the invention, with the oracle database is example, carry out when synchronous in the data that foreground and background databases is preserved, obtain defaultly in order to finishing the synchronous task definition of foreground and background databases earlier, and the task definition that will preset is divided into the plurality of sub task; Again the plurality of sub task is divided into groups, comprise at least one subtask in every group; Then, the subtask in each grouping of execution; Wherein, each tasks in parallel of dividing into groups is carried out.
Below in conjunction with accompanying drawing the preferred embodiment of the present invention is elaborated.
Consult shown in Figure 1A, in the present embodiment, need synchronous foreground and background databases to be installed in respectively in Foreground Data storehouse server and the background data base server, the synchronous flow process of foreground and background databases can be carried out by the background data base server, also can carry out by the server of special setting, in the present embodiment, be that example is introduced with the latter event.
Consult shown in Figure 1B, in the present embodiment, the server that is used to carry out the synchronous flow process of foreground and background databases comprises storage unit 100, determining unit 101, grouped element 102 and performance element 103.
Determining unit 101 is used to obtain default in order to finishing the synchronous task definition of foreground and background databases, and the task definition that will preset is divided into the plurality of sub task;
Based on above-mentioned server, to consult shown in Figure 2ly, in the present embodiment, at oracle database, it is as follows that server is carried out the detailed process that backwards and forwards data synchronization upgrades:
Step 200: obtain default task definition, promptly need to carry out the data in synchronization content.
In the present embodiment, task definition is pre-configured by managerial personnel, and preserve with the form of database table, according to what of task definition, one or more database table (hereinafter referred to as task list) can be set, for example, as shown in table 1, a task list that records task definition has comprised field name, field type and content description three class list items, wherein, field name be used to indicate the synchronous requirements of process of this foreground and background databases at data content, field type is used to indicate the data type of each data content, and content description is used for the explanation that makes an explanation of each data content.
Table 1
| Field name | Field type | Content description |
| ?Table_name | ??Varchar2(30) | Need the synchronous meter title |
| ?Owner | ??Varchar2(30) | User's name |
| ?Dblink_owner | ??Varchar2(30) | Long-range table user's name |
| ?Dblink | ??Varchar2(30) | Need synchronous dblink title |
| ?Sql_text | ??Varchar2(3000) | The sql statement of the special method of synchronization is deposited |
| ?Status | ??Number | State: 1 is the insert-truncate method of synchronization; 2 is the artificial sql of the generation statement method of synchronization; 3 is invalid; 4 is the truncate-insert method of synchronization in a plurality of storehouses; 5 is synchronous from a plurality of storehouses, and needs the method for synchronization of the artificial sql of insertion statement; 6 also need to carry out the method for synchronization of additional treatments after finishing for this module; |
| ?Module_name | ??Varchar2(30) | The title of table 1 in original synchronization module |
| ?Primary_key_value | ??number | 1 for there being major key, and 2 for not having |
| ?Primary_index_value | ??Number | 1 for there being index, and 2 are no index |
| ?Month | ??Number | Every month synchronize script is inserted every month on the synchronous date, does not then fill in 0 |
| ?Week | ??Number | Synchronize script is filled in weekly synchronous week weekly, is worth to be then not fill out 0 by 1-7 |
Step 210: default task definition is divided into the plurality of sub task, and is divided into groups in each subtask.
Generally, default task definition all can comprise several task lists as shown in table 1, in the present embodiment, a task list is provided with the subtask of a corresponding atomic level, and, dynamically generate and carry out the corresponding needed perform statement in subtask according to the title of each task list and the function of Oracle data dictionary; And what is called is divided into groups to the plurality of sub task, promptly is that some task lists are divided in the different groups.
Consult shown in Figure 3, in the present embodiment, suppose server according to table 1, determine that needing to carry out n subtask finishes the synchronous flow process of foreground and background databases, so, server can divide into groups to this n subtask according to default rule, as shown in Figure 3, in the present embodiment, n subtask has been divided into the F group, wherein, 1 group comprises subtask 1, subtask 2 and subtask 3; 2 groups comprise subtask 4, subtask 5 and subtask 6; The F group comprises subtask n-2, subtask n-1 and subtask n.
Certainly, the quantity of the subtask that comprises in every group can be according to actual conditions and relative set, on the other hand, the number of the subtask that comprises between each group can be identical, also can be inequality, it is that example is introduced that present embodiment only all comprises 3 subtasks with every group, does not repeat them here.
Step 220: the completion status that a correspondence is set for every group of subtask identifies, and in the present embodiment, whether this completion status sign is used to indicate the subtask that belongs to same group all to finish.
In the present embodiment, when the completion status of certain grouping is designated " 0 ", represent to have at least in this grouping a subtask not finish as yet, and when the completion status of certain grouping is designated " 1 ", represent that subtasks all in this grouping all finishes.
Step 230: the subtask in each grouping of beginning executed in parallel.
In the present embodiment, the subtask that belongs in the same grouping is that serial is carried out, and for example, in 1 group, subtask 1 is finished, and just begins subtasking 2.Subtask 2 is finished, and just begins subtasking 3; Simultaneously, each subtask of comprising of grouping is an executed in parallel, for example, 1 group, 2 groups ... in the F group separately the subtask of current execution be executed in parallel.Like this, just can reduce the dependence between each subtask, accelerate the execution efficient of the synchronous flow process of foreground and background databases to a certain extent, improve renewal speed.
Step 240: the completion status sign to each group detects, and judges whether to exist the grouping of the equal executed success in subtask, if then carry out step 250; Otherwise, carry out step 260.
Step 250: with the subtask all the execution concluding time of completed grouping be recorded in default task and finish in the table, had the grouping of carrying out the concluding time, will no longer detect its completion status sign; Then, carry out step 260.
Consult shown in the table 2, suppose to take turns in the detection one, the testing result that obtains is: the completion status of 1 group of correspondence is designated " 0 ", be used for indicating 1 group to have at least a subtask not finish as yet, and the corresponding completion status sign of 2 groups and F group is " 1 ", is used for indicating 2 groups and all subtasks of F group all to finish; Then execution concluding time of 2 groups and F group is recorded in task as shown in table 3 and finishes in the table, when next round detected completion status sign of each group, task was finished and is recorded each grouping of carrying out the concluding time in the table and will no longer detect.
Table 2
| Group names | The completion status sign |
| 1 group | ??0 |
| 2 groups | ??1 |
| ??…… | ??…… |
| The F group | ??1 |
Table 3
Step 260: further judge whether to exist the still uncompleted grouping in subtask, if, then carry out step 270, otherwise, carry out step 280.
In the practical application, it is a variety of to judge whether to exist the method for subtask uncompleted grouping still to have, and in the present embodiment, judges in the following ways:
The judgement task is finished the total number of each subtask of being comprised of grouping of writing down in the table, whether equal in step 210 total number according to the determined subtask of task definition of table 1 record, if equate, then there is not the still uncompleted grouping in subtask in expression, if unequal, then there is the still uncompleted grouping in subtask in expression.Aforesaid way only is a preferred implementation, and other modes repeat no more.
Step 270: wait for and set duration, return step 240.
Step 280: finish current flow process, the synchronous flow process of whole foreground and background databases is finished.
Based on the foregoing description, in order to accelerate the execution efficient of the synchronous flow process of whole foreground and background databases, preferably, can dispose a dimension table as shown in table 4, wherein, record the follow-up flow process that triggers by each subtask, in the present embodiment, so-called follow-up flow process is meant the polymerization after the synchronous flow process of foreground and background databases, treatment scheme such as gathers; In case all subtasks are finished in certain grouping, the completion status sign of i.e. this grouping is designated as " 1 ", then the follow-up flow process that is triggered by each subtask in this grouping just can come into operation, and need not to wait for that the subtask in other groupings is finished, like this, make between subtask that each grouping comprises separately, also can accelerate the execution efficient of the synchronous flow process of whole foreground and background databases to a certain extent.
Table 4
| Field name | Field type | Describe |
| ??Module_name | ??Varchar2(30) | The synchronization module title |
| ??Table_name | ??Varchar2(30) | The sql statement that needs execution |
| ??Status | ??Number | 1 is that effectively 2 is invalid |
| ??Mission_table | ??Varchar2(30) | The task list that previous task is judged |
| ??Mission_owner | ??Varchar2(30) | The user of the task list that previous task is judged |
| ??Mission_module | ??Varchar2(30) | The affiliated module of the table that the previous task source is judged |
On the other hand, in order further to accelerate the execution efficient of the synchronous flow process of whole foreground and background databases, a kind of or combination in any in can also be in the following ways:
One, if the data volume that the dimension souvenir carries of certain in the background data base is bigger, need obtain synchrodata by the different dblink from the database of foreground, then can dispose a dimension table that is used to indicate never same dblink loading data, content of this dimension table is as shown in table 5:
Table 5
| Field name | Field type | Describe |
| ??Table_name | ??Varchar2(30) | Table name claims |
| ??Dblink | ??Varchar2(30) | The DBLINK that needs synchrodata |
| ??Sql_text | ??Varchar2(3000) | The processing of special synchronization statements |
Two, in the synchronous flow process of foreground and background databases, the situation that the subtask execution error can occur, generally, the subtask that execution error occurs can be re-executed, but, these the subtask that exists a part to need not to re-execute in the subtask of execution error occurs, that is to say, even execution error appears in this part subtask, final task action result can be do not influenced yet, so, a dimension table as shown in table 6 can be disposed, be used in reference to the subtask that need not to re-execute after the existing execution error is shown, it thes contents are as follows:
Table 6
| Field name | Field type | Describe |
| ??Error_msg | ??Number | The error code that can repeat (as: the error message code of oracle) |
| ??Status | ??Number | State, 1 for repeating, and 2 for carrying out |
In the synchronous flow process of foreground and background databases, if server runs into the subtask that execution error occurs, then travel through dimension table as shown in table 5, record corresponding subtask among the Ruo Weibiao, then no longer re-execute this subtask, but directly carry out follow-up flow process; Do not record corresponding subtask among the Ruo Weibiao, then need to re-execute this subtask and finish up to successful execution.
Three, can needed all or part of perform statement be recorded in the dimension table as shown in table 7 when carrying out each subtask, in case mistake appears in the synchronous flow process of foreground and background databases, can directly determine to re-execute part or the needed perform statement of whole flow process, and need not by manually carrying out correction process according to the dimension table shown in the table 7.
Table 7
| Field name | Field type | Describe |
| ??Gmt_create | ??Date | The task date of formation |
| ??Mission_textl | ??Varchar2(3000) | The sql statement that generates |
Use one or any combination in above-mentioned three kinds of modes can realize improving the technique effect of the synchronous flow performing efficient of foreground and background databases, be not limited to wherein a kind of, do not repeat them here.
In sum, in the embodiment of the invention, when carrying out the synchronous flow process of foreground and background databases, server obtains default in order to finishing the synchronous task definition of foreground and background databases earlier, and the task definition that will preset is divided into the plurality of sub task; Again the plurality of sub task is divided into groups, comprise at least one subtask in every group; Then, carry out the subtask in each grouping, wherein, each tasks in parallel of dividing into groups is carried out.Like this, mode with respect to each subtask serial execution under the prior art, in the embodiment of the invention, the mode that belongs to executed in parallel between the subtask of different grouping makes that the subtask in each grouping is separate, thereby reduced the dependence between the subtask, shorten the required time of subtasking to a certain extent, and then improved the efficient of the synchronous flow process of foreground and background databases effectively.
Obviously, those skilled in the art can carry out various changes and modification and not break away from the spirit and scope of the present invention executing example among the present invention.Like this, if these in the embodiment of the invention are revised and modification belongs within the scope of claim of the present invention and equivalent technologies thereof, then the embodiment among the present invention also is intended to comprise these changes and modification interior.
Claims (10)
1. the method for a synchronous foreground and background databases is characterized in that, comprising:
Obtain defaultly in order to finishing the synchronous task definition of foreground and background databases, and the task definition that will preset is divided into the plurality of sub task;
The plurality of sub task is divided into groups, comprise at least one subtask in every group;
Carry out the subtask in each grouping; Wherein, each tasks in parallel of dividing into groups is carried out.
2. the method for claim 1 is characterized in that, carry out according to default order serial the subtask that belongs to same grouping.
3. method as claimed in claim 1 or 2, it is characterized in that, for each grouping is provided for indicating the sign of subtask completion status respectively, when determining that according to described sign the equal executed in subtask in a certain grouping finishes, trigger the follow-up flow process of each subtask correspondence in this grouping.
4. method as claimed in claim 1 or 2, it is characterized in that, when the subtask of carrying out in respectively dividing into groups, if execution error appears in the subtask, then with described subtask and pre-conditioned comparing, if it is described pre-conditioned that described subtask meets, then no longer re-execute this subtask, continue to carry out follow-up flow process.
5. method as claimed in claim 1 or 2, it is characterized in that, when the data in synchronization content is determined to need the subtask of execution as required, be recorded in the default allocation list carrying out the required all or part of perform statement in each subtask, when mistake appears in foreground and background databases synchronous flow journey, re-execute the flow process part that makes a mistake according to the perform statement of putting down in writing in the described allocation list.
6. a server is characterized in that, comprising:
Storage unit is used to preserve default task definition;
Determining unit is used to obtain default in order to finishing the synchronous task definition of foreground and background databases, and the task definition that will preset is divided into the plurality of sub task;
Grouped element is used for the plurality of sub task is divided into groups, and comprises at least one subtask in every group;
Performance element, the subtask that is used for carrying out each grouping; Wherein, each tasks in parallel of dividing into groups is carried out.
7. server as claimed in claim 6 is characterized in that, comprising: described performance element is carried out the subtask that belongs to same grouping according to default order serial.
8. as claim 6 or 7 described servers, it is characterized in that, described grouped element is provided for indicating the sign of subtask completion status respectively for each grouping, when described performance element determines that according to described sign the equal executed in subtask in a certain grouping finishes, trigger the follow-up flow process of each subtask correspondence in this grouping.
9. as claim 6 or 7 described servers, it is characterized in that, described performance element is when the subtask of carrying out in respectively dividing into groups, if execution error appears in the subtask, then with described subtask and pre-conditioned comparing, if it is described pre-conditioned that described subtask meets, then no longer re-execute this subtask, continue to carry out follow-up flow process.
10. as claim 6 or 7 described servers, it is characterized in that, described determining unit as required the data in synchronization content determine to need carry out the subtask time, be recorded in the default allocation list carrying out the required all or part of perform statement in each subtask, when described performance element mistake occurs in the synchronous flow process of foreground and background databases, re-execute the flow process part that makes a mistake according to the perform statement of putting down in writing in the described allocation list.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN200810239529A CN101751429A (en) | 2008-12-12 | 2008-12-12 | Method and device for synchronizing foreground database and background database |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN200810239529A CN101751429A (en) | 2008-12-12 | 2008-12-12 | Method and device for synchronizing foreground database and background database |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN101751429A true CN101751429A (en) | 2010-06-23 |
Family
ID=42478420
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN200810239529A Pending CN101751429A (en) | 2008-12-12 | 2008-12-12 | Method and device for synchronizing foreground database and background database |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN101751429A (en) |
Cited By (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102929698A (en) * | 2012-09-29 | 2013-02-13 | 北京百度网讯科技有限公司 | Task re-judgment method and system |
| CN103500229A (en) * | 2013-10-24 | 2014-01-08 | 北京奇虎科技有限公司 | Database synchronization method and database system |
| CN106358003A (en) * | 2016-08-31 | 2017-01-25 | 华中科技大学 | Video analysis and accelerating method based on thread level flow line |
| CN106844694A (en) * | 2017-01-24 | 2017-06-13 | 恒生电子股份有限公司 | For the method and apparatus of synchrodata |
| CN108021431A (en) * | 2016-11-04 | 2018-05-11 | 广东亿迅科技有限公司 | Method and its system based on web data interactive maintenance Hive |
| CN108573006B (en) * | 2017-06-06 | 2021-03-26 | 北京金山云网络技术有限公司 | Cross-machine-room data synchronization system, method and device and electronic equipment |
| CN112860392A (en) * | 2021-01-15 | 2021-05-28 | ***股份有限公司 | Data processing method, device, equipment and medium |
| CN113377863A (en) * | 2020-03-10 | 2021-09-10 | 阿里巴巴集团控股有限公司 | Data synchronization method and device, electronic equipment and computer readable storage medium |
-
2008
- 2008-12-12 CN CN200810239529A patent/CN101751429A/en active Pending
Cited By (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102929698A (en) * | 2012-09-29 | 2013-02-13 | 北京百度网讯科技有限公司 | Task re-judgment method and system |
| CN103500229A (en) * | 2013-10-24 | 2014-01-08 | 北京奇虎科技有限公司 | Database synchronization method and database system |
| CN103500229B (en) * | 2013-10-24 | 2017-04-19 | 北京奇虎科技有限公司 | Database synchronization method and database system |
| CN106358003A (en) * | 2016-08-31 | 2017-01-25 | 华中科技大学 | Video analysis and accelerating method based on thread level flow line |
| CN106358003B (en) * | 2016-08-31 | 2019-02-19 | 华中科技大学 | A kind of video analysis accelerated method based on thread level production line |
| CN108021431A (en) * | 2016-11-04 | 2018-05-11 | 广东亿迅科技有限公司 | Method and its system based on web data interactive maintenance Hive |
| CN106844694A (en) * | 2017-01-24 | 2017-06-13 | 恒生电子股份有限公司 | For the method and apparatus of synchrodata |
| CN106844694B (en) * | 2017-01-24 | 2019-11-15 | 恒生电子股份有限公司 | Method and apparatus for synchrodata |
| CN108573006B (en) * | 2017-06-06 | 2021-03-26 | 北京金山云网络技术有限公司 | Cross-machine-room data synchronization system, method and device and electronic equipment |
| CN113377863A (en) * | 2020-03-10 | 2021-09-10 | 阿里巴巴集团控股有限公司 | Data synchronization method and device, electronic equipment and computer readable storage medium |
| CN113377863B (en) * | 2020-03-10 | 2022-04-29 | 阿里巴巴集团控股有限公司 | Data synchronization method and device, electronic equipment and computer readable storage medium |
| CN112860392A (en) * | 2021-01-15 | 2021-05-28 | ***股份有限公司 | Data processing method, device, equipment and medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN101419615B (en) | Method and apparatus for synchronizing foreground and background databases | |
| CN101751429A (en) | Method and device for synchronizing foreground database and background database | |
| CN102725753B (en) | Method and apparatus for optimizing data access, method and apparatus for optimizing data storage | |
| CN113874852A (en) | Indexing for evolving large-scale datasets in a multi-master hybrid transaction and analytics processing system | |
| US8396862B2 (en) | Product join dynamic partition elimination for multilevel partitioning | |
| US8738673B2 (en) | Index partition maintenance over monotonically addressed document sequences | |
| CN108683692B (en) | Service request processing method and device | |
| CN102129425B (en) | The access method of big object set table and device in data warehouse | |
| CN105608086A (en) | Transaction processing method and device of distributed database system | |
| CN103092903A (en) | Database Log Parallelization | |
| CN101650742B (en) | System and method for prompting search condition during English search | |
| CN105989059A (en) | Data record checking method and device | |
| CN109714249B (en) | Method and related device for pushing applet messages | |
| CN106612330B (en) | System and method for supporting distributed multi-file import | |
| CN111722918A (en) | Service identification code generation method and device, storage medium and electronic equipment | |
| CN111797604A (en) | Report generation method, device, equipment and computer readable storage medium | |
| CN103246549A (en) | Method and system for data transfer | |
| CN111324604A (en) | Database table processing method and device, electronic equipment and storage medium | |
| CN111651453A (en) | User historical behavior query method and device, electronic equipment and storage medium | |
| CN110580255A (en) | method and system for storing and retrieving data | |
| US20040015520A1 (en) | Database managing method and system having data backup function and associated programs | |
| CN103809915B (en) | The reading/writing method of a kind of disk file and device | |
| CN109446271B (en) | Data synchronization method, device, equipment and medium | |
| CN111580972A (en) | Virtual resource processing method and device | |
| CN115269548A (en) | Method and system for generating data warehouse development model and related equipment |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C12 | Rejection of a patent application after its publication | ||
| RJ01 | Rejection of invention patent application after publication |
Open date: 20100623 |