CN101183361A - Method of relation data base applications automatic upgrade - Google Patents
Method of relation data base applications automatic upgrade Download PDFInfo
- Publication number
- CN101183361A CN101183361A CNA200610114522XA CN200610114522A CN101183361A CN 101183361 A CN101183361 A CN 101183361A CN A200610114522X A CNA200610114522X A CN A200610114522XA CN 200610114522 A CN200610114522 A CN 200610114522A CN 101183361 A CN101183361 A CN 101183361A
- Authority
- CN
- China
- Prior art keywords
- data
- tables
- edition
- edition data
- field
- 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
Images
Landscapes
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
- Stored Programmes (AREA)
Abstract
The invention discloses an automatic upgrade method applied to the relational data base, which comprises the following steps: the data base structure of an objective version is created; the data base structure of the source version is scanned and analyzed by the automatic upgrade system of the data base, so as to obtain the data base structure information of the source version; the data base structure of the objective version is scanned and analyzed by the automatic upgrade system of the data base, so as to obtain the data base structure information of the objective version; the data base structure information of the source version and the objective version is compared and analyzed to generate an upgrade strategy automatically; the upgrade is executed according to the upgrade strategy. The data base information of the source version and the objective version is factually and completely reflected through automatically analyzing and upgrading the data base structure of the source version and the objective version and automatically generating the upgrade strategy, thus the information disjunction between an upgrade tool and a field version likely caused by the subjective surmise of customizing and compiling upgrade tool is avoided, and the upgrade and the rolling back of the data base between the arbitrary versions can be conveniently and flexibly completed.
Description
Technical field
The present invention relates to a kind of upgrade method, particularly relate to the automatically updating method that a kind of relational database is used.
Background technology
For satisfying the needs of current miscellaneous service exploitation, operation management, equipment or software product supplier have developed various business softwares based on commercial data library softwares such as MS SQL, Oracle, Sybase.Principal mode is to utilize the commercial data base software creation to take the database entity of certain storage size, a series of relation database table, may also have database elements such as storing process, trigger.But because the upgrading to service database system will frequently take place in the continuing to bring out of new business new demand, the growth of portfolio, the fault restoration and the increased functionality of software version.The upgrading of database mainly comprises change of elements such as the modification, storing process in change, the space of additions and deletions, the list structure of table etc.For this paper narrates conveniently, we are referred to as upgrading source version to original subscriber's data base set of needs upgrading, and the target user data storehouse system after the upgrading is called the upgrading target version.Traditional upgrade method is to come customized development edition upgrading instrument by the research staff according to the characteristic of upgrading source version, upgrading target version.This upgrading tool is closely related with upgrading source version, upgrading target version, is drawn by the artificial difference of analyzing two versions of research staff, and this upgrade method has following shortcoming:
1, can not itself judge whether that modification has taken place two version spatial database structures from the customer data base system, can only judge which database structure has had modification in the version according to the version number of version, this judgement error can occur unavoidably.For example some fails to be reacted in the variation of version number for the modification of database, cause different database structure (may be very small) to correspond in the same version number, at this moment the database upgrade instrument that customizes according to version number just can not entirely truely be upgraded.Might be on-the-spot in the product operation, the user carried out some modifications, and perhaps some changes were done at the technical support personnel scene, and at this moment Ding Zhi database upgrade instrument can't change at these scenes of perception;
2, when carrying out edition upgrading, can occur manyly in theory, like this, rely on different editions number to come the customized version upgrading tool, will make data upgrading tool maintenance workload along with the increase of version number sharply increases to many multiple version conversion situations.When redaction of issue, must make the upgrading tool that is upgraded to redaction at all versions before this.Can certainly pass through alternative, such as carrying out the echelon upgrading, progressively be upgraded to latest edition, but this can cause escalation process loaded down with trivial details, consuming time, error probability strengthens;
3, the edition upgrading instrument of this customization rollback after the failure that also is unfavorable for upgrading.Because upgrading tool itself can not be discerned the internal data library structure of different editions, so reverse rollback also need customize at different editions, wastes time and energy.
If can realize a kind of method, data structure characteristic to the relational database of upgrading source version, upgrading target version is analyzed automatically, generates escalation policy then, finally carries out auto-update by this strategy, then can overcome the above problems, realize convenient, flexible relation data auto-update.Very big for some database structure difference, the user need customize escalation policy, also can provide automatic analysis result, makes the user carry out part on this basis and specifies escalation policy, thereby realize accurately complete upgrading.
Summary of the invention
Problem to be solved by this invention is, a kind of method of relation data base applications automatic upgrade is provided, with auto-update convenient, flexible between the database that is implemented in any version.
To achieve these goals, the invention discloses a kind of method of relation data base applications automatic upgrade, be used to realize upgrading from edition data storehouse, source to purpose edition data storehouse, described relational database is arranged on the computing machine, also be provided with the database automatic updating system that is used to control described relational database on the described computing machine, this method comprises the steps:
Create purpose edition data library structure;
The described source of described database automatic updating system scanning analysis edition data library structure is to obtain described source edition data library structure information;
The described purpose edition data of described database automatic updating system scanning analysis library structure is to obtain described purpose edition data library structure information;
The described source of comparative analysis, purpose edition data library structure information generate escalation policy;
Carry out upgrading according to described escalation policy.
The described source of described comparative analysis, purpose edition data library structure information, the step that generates escalation policy further comprises:
For the newly-increased tables of data of the relative source of described purpose edition data library structure edition data library structure, generate the escalation policy of creating described tables of data;
Perhaps, be not present in the tables of data of described purpose edition data library structure for only being present in described source edition data library structure, generate the escalation policy of ignoring described tables of data;
Perhaps, for the newly-increased field of the relative source of described purpose edition data library structure edition data library structure, generate the escalation policy of creating described field;
Perhaps, be not present in the field of described purpose edition data library structure for only being present in described source edition data library structure, generate the escalation policy of ignoring described field;
Perhaps, for the same field with compatible attribute of the identical data table in described source, purpose edition data library structure, generate the directly escalation policy of upgrading;
Perhaps, for storing process, trigger of the same name in described source, purpose edition data library structure, generate the escalation policy of directly replacing upgrading.
The described source of described comparative analysis, purpose edition data library structure information, the step that generates escalation policy further comprises:
Step 1, described database automatic updating system is an index with the tables of data table name in described purpose edition data storehouse, successively the table name of the tables of data in purpose edition data storehouse and each tables of data table name in edition data storehouse, source are compared, judge whether identical, if it is identical, change step 2,, change step 3 if different;
Step 2, with the index by name of the field in the described tables of data, successively each field name in the described tables of data in field name in the described tables of data in described purpose edition data storehouse and edition data storehouse, described source is compared, identical to judge whether, if it is identical, change step 4,, change step 5 if different;
Step 3 is created on the escalation policy of creating described tables of data in the described purpose edition data storehouse, if step 1 is changeed in the not all contrast end of the tables of data in described purpose edition data storehouse, otherwise changes the step of described execution upgrading;
Step 4 judges that the attribute of described field in described purpose edition data storehouse is whether compatible with the attribute of the described field in edition data storehouse, described source, if compatible, changes step 6;
Step 5, be created on the escalation policy of creating described field in the described tables of data in described purpose edition data storehouse, if the field of described tables of data is all contrast end not, change step 2, if all contrasting, the field of described tables of data finishes but not all contrast end of tables of data in described purpose edition data storehouse, change step 1,, change the step of described execution upgrading if all contrast finishes;
Step 6, generate the directly escalation policy of upgrading, if the field of described tables of data is all contrast end not, change step 2, if all contrasting, the field of described tables of data finishes but not all contrast end of tables of data in described purpose edition data storehouse, change step 1,, change the step of described execution upgrading if all contrast finishes.
Described method also comprises: for field newly-increased in the described purpose edition data library structure is inserted the default value that has been provided with.
The escalation policy of the described direct upgrading of described execution further comprises:
The data of the described field of tables of data described in the edition data storehouse, described source are directly inserted in the described field of tables of data described in the described purpose edition data storehouse.
The step of the described source of described database automatic updating system scanning analysis, purpose edition data library structure is that the mode of the system's table by analyzing described source, purpose edition data storehouse realizes.
The described source of described comparative analysis, purpose edition data library structure information, the step that generates escalation policy also comprises afterwards: show described source, purpose edition data library structure information, the tables of data in perhaps described source, purpose edition data storehouse, the transformational relation figure of field in the graphic user interface mode.
The tables of data in described source, purpose edition data storehouse, the transformational relation figure of field can be by manual adjustment.
Described step of upgrading according to described escalation policy also comprises afterwards: carry out plug-in upgrade patch.
Also comprise after the described step 4,, carry out plug-in upgrade patch if incompatible.
The present invention is by analyzing the database structure of upgrading source version, purpose version automatically, automatically generate escalation policy, the database information that has reflected source version, purpose version truely and completely, the upgrading tool of having avoided the subjectivity of custom-written upgrading tool to conjesture may causing and the information disconnection of live version can be finished database upgrade and rollback between any version easily and flexibly.
Description of drawings
Fig. 1 is that relational database of the present invention is arranged at the one-piece construction synoptic diagram on the server;
Fig. 2 is the structural representation of database of the present invention;
Fig. 3,4 is for the detailed step process flow diagram of auto-update of the present invention;
Fig. 5 is presented at the user to operate the source on the display interface, the database structure figure of purpose version.
Embodiment
In order to allow above-mentioned purpose of the present invention, advantage and the feature can be clearer, be elaborated below in conjunction with embodiment.But following embodiment and accompanying drawing also are not used in the scope of the present invention that limits.
What the present invention realized is a kind of method of auto-update of relational database application.Be that promptly upgrading object is not a business database system itself at the customer data base system based on the exploitation of commercial relations Database Systems, but the content of customer data base.
Figure 1 shows that relational database of the present invention is arranged at the one-piece construction synoptic diagram on the server.As shown in the figure, server 1 is provided with relational database 10, and this sentences single customer data base system is example, but is not limited thereto.Wherein, concrete composition structure comprises: database automatic updating system 100, database 200, user operate display interface 300, operating system 400.Database automatic updating system 100 is the foundation for database, the software that operation and maintenance is provided with.It is based upon on the basis of operating system 400, is a kind of data management software between operating system and user, is responsible for unified management and control are carried out in the database application upgrade.The user operates various orders relevant with updating operation in that send or the application program of display interface 300 by the user, all will carry out by database automatic updating system 100.Store various relation database tables and system data table in the database 200, specifically describe and see Fig. 2.Operating system 400 provides run time infrastructure for other all modules.
In user's actual application, the upgrading that relational database is used is usually directed to: newly-increased tables of data, tables of data increase attribute field, the expansion of data sheet field attribute.For the compatibility of version before and after guaranteeing to upgrade, the process of upgrading should be followed following principle:
1, the same tables of data table name of new and old edition should remain unchanged;
2, its field name of same field in the same tables of data of new and old edition should remain unchanged;
3, its field attribute should be compatible before and after the same field upgrading;
4, newly-increased tables of data directly increases;
5, new field directly increases, if be provided with default value, then inserts default value;
6, exist in the legacy version, but the tables of data that redaction does not have, field are ignored in escalation process automatically;
7, directly replace upgrading for database objects such as storing process of the same name, triggers.
The detailed step of the method for auto-update of the present invention is described below in conjunction with Fig. 3,4.
At first, create purpose edition data library structure (step 301).The user can utilize the user to operate display interface 300 input data, what redaction was set is the database structure of purpose version, and be stored in the newdata library storage unit 202 of database 200, similar with current version storage unit 201, also comprise with the corresponding system of the database structure of this purpose version table in this newdata library storage unit 202.This purpose edition data storehouse relatively source version deleted the partial data table, increased tables of data, the attribute that expanded field or field change.
If this moment, the user operated the order that display interface 300 sends upgrading by the user, after then database automatic updating system 100 is received order, respectively source edition data library structure and purpose edition data library structure are carried out scanning analysis (step 302).For edition data storehouse, source, can be by analyzing the mode of system's tables such as sysobjects, obtain database element information such as all tables of data, data field, storing process, trigger, default value, index, by analyzing the details that syscolumns can obtain each table.Concrete scanning implementation procedure for example is:
Select?name，colid，usertype，length，prec，scale，Status，cDefaultfrom?syscolumns?where?object_name(id)＝TableName?order?by?ColID。
And analysis result is stored in the current version storage unit 201 of database 200 according to specific format.For purpose edition data storehouse, adopt system's tables such as same methods analyst sysobjects, syscolumns, obtain all information of purpose edition data storehouse, be stored in the newdata library storage unit 202 of database 200 according to specific format equally.The database structure of this purpose version behind scanning analysis can be as Template Information, so that single pass, follow-up can repeatedly reading for the database automatic updating system.
Utilize database automatic updating system 100 comparative analysis sources, purpose edition data library structure information, automatically generate escalation policy (step 303), this escalation policy embodies by the mode of upgrading SQL script, automatically generate, correspondence is finished and is created new data table, trigger, storing process etc., perhaps realize extracting in the legacy data table data and be inserted in the new data table, and upgrade script is stored in the database.This step 303 specifically comprises:
Directly replace upgrading (step 400) for database objects such as storing process of the same name, triggers.If not of the same name, then need to create again.
Tables of data table name with purpose edition data storehouse is an index, successively the table name of the tables of data in purpose edition data storehouse and each tables of data table name in edition data storehouse, source is compared, and judges whether identical (step 401).As find that source, purpose edition data have identical table name in the storehouse, and then think same table, will change step 402 to the further comparative analysis of their list structure.Otherwise just think two incoherent tables of data, can't respective upgrades, unless the user by GUI (graphic user interface) mode manual adjustment escalation policy, and changes step 404.
In the described identical data table in source, purpose edition data storehouse, as index, successively the field name in purpose edition data storehouse and each field name in edition data storehouse, source are compared, to judge whether identical (step 402) with field name.If in the identical data table in source, purpose edition data storehouse, have identical field name, then attribute is further analyzed, change step 403, if find different fields, then think two independently data fields, can't respective upgrades, unless the user by GUI mode manual adjustment escalation policy, and changes step 405.
In the same field of the identical data table in source, purpose edition data storehouse, judge attribute whether compatible (step 403).If judge in the purpose edition data storehouse that this field attribute is incompatible fully in this field attribute and edition data storehouse, source, then the pairing data of this field can't be upgraded in the purpose edition data storehouse in this tables of data respective field in the source edition data storehouse, according to the upgrading principle, run into this situation and will take the processing mode refusing to upgrade, but the user can realize upgrading (step 4032) by the mode of carrying out plug-in upgrade patch, if attribute is compatible fully, can respective upgrades (step 4031), promptly the data of this field are directly inserted in the corresponding field of source version in the purpose version.So-called attribute is compatible, is meant that promptly the character string capacity increases, and integer value capacity increases, and the integer value is converted into character string etc.
The situation of step 404, this situation newly-increased tables of data in can unique corresponding purpose edition data storehouse, therefore direct this tables of data of establishment in purpose edition data storehouse.If promptly there is the situation that does not have certain table in the purpose edition data storehouse and this table is arranged in the edition data storehouse, source, then should be called the mode that index compares with tables of data in the purpose version, can directly ignore this tables of data.
The situation of step 405, this situation new field in can unique corresponding purpose edition data storehouse corresponding data table is directly created this field, if be provided with default value, then inserts default value.Compare with the method for the invention, can directly ignore the field that does not have in the purpose edition data storehouse and have in the edition data storehouse, source.
Also comprise after the described step 4031,4032,405, if the field of described tables of data is all contrast end not, change step 402 and continue to finish contrast, if all contrasting, the field of described tables of data finishes but not all contrast end of tables of data in described purpose edition data storehouse, change step 401, if all contrast finishes, continue follow-up step.
Also comprise after the described step 404, if the not all contrast end of the tables of data in described purpose edition data storehouse are changeed step 401, otherwise continued follow-up step.
In the above-mentioned deterministic process automatically generate,, generate calling when carrying out upgrading automatically as respective upgrades, the escalation policy that increases field/table name or directly ignore in the mode of upgrade script.And the strategy of so-called respective upgrades is the correspondence position that data in the edition data storehouse, source can directly be stored in purpose edition data storehouse.The strategy of directly ignoring is the corresponding data in the edition data storehouse, source, is left in the basket, and can not be stored in the purpose edition data storehouse.
Above-mentioned deterministic process shows that the source exists in the edition data storehouse, but the tables of data that the purpose version does not have, field are ignored in escalation process automatically; These tables of data should be to have gone out of use in purpose edition data storehouse, or some temporary tables, there is no need to upgrade.Certainly, if some tables of data is dynamically to generate in the course of the work, need be upgraded in the purpose version, then the user can follow-uply manually be provided with upgrading by the GUI mode.Tables of data, field newly-increased in the purpose version all directly increase.
Source after the above-mentioned scanning, purpose edition data library structure characteristic, and the escalation policy that generates will operate on the display interface 300 the user with the GUI form and present to the user, confirm that for the user user also can the above-mentioned escalation policy of manual adjustment (step 304).Confirm if obtain, the user will operate the instruction that display interface 300 sends upgrading by the user, start the process of upgrading, and then database will be according to the escalation policy that has been provided with upgrade (step 305), promptly carry out the SQL upgrade script of escalation policy correspondence, then upgrading is finished.
But need depend on the User Defined escalation policy for following unconventional situation, perhaps plug-in upgrade patch is finished:
1, table name, field name change;
2, tables of data not of the same name, the data-switching between the field;
3, the batch assignment of newly-increased tables of data, new field.
During in the face of above-mentioned situation, the user can manually be provided with escalation policy by the GUI mode in step 304, after step 305, also needs execution in step 306 simultaneously, promptly carries out the step of plug-in upgrade patch.
Below be example with a student information management system, implementation procedure of the present invention is described.
The V1.0 of student information management system comprises four tables of data: student's Basic Information Table, student's history information table, student performance Track Table, the qualified teachers of class allocation list.Its middle school student's Basic Information Table comprises following field: name, sex, date of birth, class.The attribute of name field is a character type, and supports 8 characters to be applicable to the name of the longest 4 Chinese characters.
The user operates the one-piece construction that display interface has been set up the V2.0 of student information management system of redaction by the user, and is kept in the server.The function expansion that it carried out comprises: increased student's fitness Track Table, student's social activities Track Table.Simultaneously, for student's Basic Information Table, also done following variation:
1, expands the attribute of " name " field, expanded to the expression scope of 40 characters;
2, newer field " contact method ", " father ", " mother ", " home address " have been increased.
Because several thousand people's student information has been arranged among the V1.0 of student information management system, for the tables of data content synchronization among the V1.0 in V2.0, just need carry out the upgrading of this database.
The user operates display interface by the user immediately, for example utilizes the mode of keyboard input instruction, sends the upgrading order.After the database structure characteristics of 100 pairs of sources of database automatic updating system, purpose version scan contrast, operate on the display interface source that shows as shown in Figure 5, the database structure figure of purpose version the user.Here the information that has mainly shown tables of data, literary name section, certainly, constraint conditions such as the type of refinement display field successively, size, default value, database element information such as storing process, and the transformational relation figure of each tables of data, field in the escalation policy, so that the process of the more clear and intuitive understanding upgrading of user.
Find through the overscanning contrast, V2.0 has increased table name " student's fitness Track Table ", " student's social activities Track Table " newly, increase field " contact method ", " father ", " mother ", " home address " newly, expanded the attribute of " name " field.For newly-increased table, owing to do not have related content among the V1.0, therefore directly increase new table and get final product, newly-increased field is then created this field automatically and is inserted default value and gets final product." name " field is because the expansion of attribute is compatible before and after being, so also can directly upgrade.The upgrade script of database automatic updating system 100 corresponding generations for example is:
Create table student fitness Track Table (Name char (20) NULL, HealthStatusTINYINT NULL DEFAULT 0, Detail Inf char (200))
Create table student social activities Track Table (Name char (20) NULL, SocialActchar (200))
Create table new student Basic Information Table (Name Char (20) NULL, Gender TINYINTNULL DEFAULT 0, Birth Char (20) NULL, Class Char (20) NULL, Contact Char (20) NULL, Father Char (20) NULL, Mother Char (20) NULL, Addr Char (50) NULL)
Insert into new student Basic Information Table select
Name, Gender, Birth, Class, NULL, NULL, NULL, NULL from student Basic Information Table
Rename table student Basic Information Table old student Basic Information Table
Rename table new student Basic Information Table student Basic Information Table
If the user need change table name when carrying out respective upgrades, for example, desire is gone into the updating content of " student's history information table " in " student performance Track Table ", can be when interface as shown in Figure 5, the upgrading association of manual adjustment data realizes by plug-in upgrade patch.
When the user to the database structure figure/transition diagram of source, purpose version and upgrade script examination confirm by the time, sending and confirming the upgrading order, then the database automatic updating system will be upgraded according to the content of upgrade script.If the user need carry out the upgrading of unconventional situation, then also need extra the startup to carry out some plug-in upgrade patch, thereby finish the process of upgrading.
The method of the invention also can reversely be carried out, and promptly rolls back to previous versions from current version, makes data base administration convenient more.
The present invention is by analyzing the database structure of upgrading source version, purpose version automatically, automatically generate escalation policy, the database information that has reflected source version, purpose version truely and completely, the upgrading tool of having avoided the subjectivity of custom-written upgrading tool to conjesture may causing and the information disconnection of live version can be finished database upgrade and rollback between any version easily and flexibly.
The above only is a best possible embodiments of the present invention, non-inflexible limit claim of the present invention, and the equivalence that all utilizations instructions of the present invention and accompanying drawing are done changes, and all in like manner is included in the scope of the present invention.
Claims (10)
1. the method for a relation data base applications automatic upgrade, be used to realize upgrading from edition data storehouse, source to purpose edition data storehouse, described relational database is arranged on the computing machine, also be provided with the database automatic updating system that is used to control described relational database on the described computing machine, it is characterized in that this method comprises the steps:
Create purpose edition data library structure;
The described source of described database automatic updating system scanning analysis edition data library structure is to obtain described source edition data library structure information;
The described purpose edition data of described database automatic updating system scanning analysis library structure is to obtain described purpose edition data library structure information;
The described source of comparative analysis, purpose edition data library structure information generate escalation policy;
Carry out upgrading according to described escalation policy.
2. the method for claim 1 is characterized in that, the described source of comparative analysis, purpose edition data library structure information, and the step that generates escalation policy further comprises:
For the newly-increased tables of data of the relative source of described purpose edition data library structure edition data library structure, generate the escalation policy of creating described tables of data;
Perhaps, be not present in the tables of data of described purpose edition data library structure for only being present in described source edition data library structure, generate the escalation policy of ignoring described tables of data;
Perhaps, for the newly-increased field of the relative source of described purpose edition data library structure edition data library structure, generate the escalation policy of creating described field;
Perhaps, be not present in the field of described purpose edition data library structure for only being present in described source edition data library structure, generate the escalation policy of ignoring described field;
Perhaps, for the same field with compatible attribute of the identical data table in described source, purpose edition data library structure, generate the directly escalation policy of upgrading;
Perhaps, for storing process, trigger of the same name in described source, purpose edition data library structure, generate the escalation policy of directly replacing upgrading.
3. method as claimed in claim 2 is characterized in that, the described source of comparative analysis, purpose edition data library structure information, and the step that generates escalation policy further comprises:
Step 1, described database automatic updating system is an index with the tables of data table name in described purpose edition data storehouse, successively the table name of the tables of data in purpose edition data storehouse and each tables of data table name in edition data storehouse, source are compared, judge whether identical, if it is identical, change step 2,, change step 3 if different;
Step 2, with the index by name of the field in the described tables of data, successively each field name in the described tables of data in field name in the described tables of data in described purpose edition data storehouse and edition data storehouse, described source is compared, identical to judge whether, if it is identical, change step 4,, change step 5 if different;
Step 3 is created on the escalation policy of creating described tables of data in the described purpose edition data storehouse, if step 1 is changeed in the not all contrast end of the tables of data in described purpose edition data storehouse, otherwise changes the step of described execution upgrading;
Step 4 judges that the attribute of described field in described purpose edition data storehouse is whether compatible with the attribute of the described field in edition data storehouse, described source, if compatible, changes step 6;
Step 5, be created on the escalation policy of creating described field in the described tables of data in described purpose edition data storehouse, if the field of described tables of data is all contrast end not, change step 2, if all contrasting, the field of described tables of data finishes but not all contrast end of tables of data in described purpose edition data storehouse, change step 1,, change the step of described execution upgrading if all contrast finishes;
Step 6, generate the directly escalation policy of upgrading, if the field of described tables of data is all contrast end not, change step 2, if all contrasting, the field of described tables of data finishes but not all contrast end of tables of data in described purpose edition data storehouse, change step 1,, change the step of described execution upgrading if all contrast finishes.
4. method as claimed in claim 3 is characterized in that, also comprises:
For field newly-increased in the described purpose edition data library structure is inserted the default value that has been provided with.
5. method as claimed in claim 2 is characterized in that, the escalation policy of carrying out described direct upgrading further comprises:
The data of the described field of tables of data described in the edition data storehouse, described source are directly inserted in the described field of tables of data described in the described purpose edition data storehouse.
6. as claim 1,2,3,4 or 5 described methods, it is characterized in that, the step of the described source of described database automatic updating system scanning analysis, purpose edition data library structure is that the mode of the system's table by analyzing described source, purpose edition data storehouse realizes.
7. as claim 1,2,3,4 or 5 described methods, it is characterized in that, the described source of comparative analysis, purpose edition data library structure information, the step that generates escalation policy also comprises afterwards: show described source, purpose edition data library structure information, the tables of data in perhaps described source, purpose edition data storehouse, the transformational relation figure of field in the graphic user interface mode.
8. method as claimed in claim 7 is characterized in that, the tables of data in described source, purpose edition data storehouse, the transformational relation figure of field can be by manual adjustment.
9. method as claimed in claim 7 is characterized in that, described step of upgrading according to described escalation policy also comprises afterwards:
Carry out plug-in upgrade patch.
10. method as claimed in claim 3 is characterized in that, also comprises after the described step 4, if incompatible, carries out plug-in upgrade patch.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNB200610114522XA CN100570604C (en) | 2006-11-13 | 2006-11-13 | A kind of method of relation data base applications automatic upgrade |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNB200610114522XA CN100570604C (en) | 2006-11-13 | 2006-11-13 | A kind of method of relation data base applications automatic upgrade |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN101183361A true CN101183361A (en) | 2008-05-21 |
| CN100570604C CN100570604C (en) | 2009-12-16 |
Family
ID=39448642
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CNB200610114522XA Expired - Fee Related CN100570604C (en) | 2006-11-13 | 2006-11-13 | A kind of method of relation data base applications automatic upgrade |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN100570604C (en) |
Cited By (33)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101859254A (en) * | 2009-04-02 | 2010-10-13 | 国际商业机器公司 | Automatically recommending upgrade approach for customizable software product |
| CN101908064A (en) * | 2010-07-20 | 2010-12-08 | 中兴通讯股份有限公司 | Data base backup recovery method and device |
| CN102065413A (en) * | 2010-11-17 | 2011-05-18 | 北京北方烽火科技有限公司 | Database updating method and system, and base station self-starting method and system |
| CN102096671A (en) * | 2009-12-14 | 2011-06-15 | 深圳速浪数字技术有限公司 | Method and equipment for generating business and operation support system (BOSS) database upgrading script |
| CN102411588A (en) * | 2010-09-26 | 2012-04-11 | 金蝶软件（中国）有限公司 | Comparison checking method and system of data table |
| CN102890720A (en) * | 2012-10-16 | 2013-01-23 | 南京通达海信息技术有限公司 | Database inspection and maintenance method |
| CN102902818A (en) * | 2012-10-26 | 2013-01-30 | 杭州迪普科技有限公司 | Method and device for upgrading database |
| CN102902707A (en) * | 2012-08-01 | 2013-01-30 | 杭州华三通信技术有限公司 | Method for realizing compatibility of binary data with different versions and data version converting system |
| CN101533356B (en) * | 2009-04-21 | 2013-02-27 | 华为技术有限公司 | A method, a device and a system for realizing software online upgrade |
| CN103294724A (en) * | 2012-03-05 | 2013-09-11 | 百度在线网络技术（北京）有限公司 | Method for managing database structures and system for method |
| CN103946794A (en) * | 2011-09-30 | 2014-07-23 | Emc公司 | Cross-reference and priority claim to related applications |
| CN104216948A (en) * | 2014-08-12 | 2014-12-17 | 上海新炬网络技术有限公司 | Difference control method of data model |
| CN104572644A (en) * | 2013-10-10 | 2015-04-29 | 北京大学 | Database updating device and database updating method |
| CN104714957A (en) * | 2013-12-13 | 2015-06-17 | 阿里巴巴集团控股有限公司 | List structure changing method and device |
| CN104750774A (en) * | 2014-12-15 | 2015-07-01 | 北京星网锐捷网络技术有限公司 | Database upgrading method and device |
| CN104881455A (en) * | 2015-05-20 | 2015-09-02 | 深圳市酷开网络科技有限公司 | Structural difference processing method and system based on MYSQL |
| CN104951550A (en) * | 2015-06-25 | 2015-09-30 | 走遍世界（北京）信息技术有限公司 | Data storage method and device |
| CN105224361A (en) * | 2015-09-15 | 2016-01-06 | 深圳市华讯方舟软件信息科技有限公司 | A kind of method and system that sqlite3 type embedded database is upgraded |
| CN105335436A (en) * | 2014-08-11 | 2016-02-17 | 方正国际软件(北京)有限公司 | Method and equipment for upgrading database structure |
| US9330122B2 (en) | 2011-09-30 | 2016-05-03 | Emc Corporation | System and method of dynamic data object upgrades |
| CN105989089A (en) * | 2015-02-12 | 2016-10-05 | 阿里巴巴集团控股有限公司 | Data comparison method and device |
| CN106156052A (en) * | 2015-03-27 | 2016-11-23 | 中兴通讯股份有限公司 | Terminal data upgrade method and device |
| CN106250485A (en) * | 2016-07-29 | 2016-12-21 | 北京北信源软件股份有限公司 | Database upgrade method, Apparatus and system |
| CN106339500A (en) * | 2016-09-09 | 2017-01-18 | 浪潮软件股份有限公司 | Remote database comparison tool and method |
| CN106777025A (en) * | 2016-12-08 | 2017-05-31 | 北京中电普华信息技术有限公司 | A kind of analysis method and system of database physical model |
| CN108023920A (en) * | 2016-10-28 | 2018-05-11 | 阿里巴巴集团控股有限公司 | A kind of data pack transmission method, equipment and application interface |
| CN108431769A (en) * | 2016-01-21 | 2018-08-21 | 微软技术许可有限责任公司 | The database and service upgrade of no shutdown time |
| CN108614868A (en) * | 2018-04-16 | 2018-10-02 | 北京酷我科技有限公司 | A kind of database automatically updating method |
| CN109388676A (en) * | 2018-08-21 | 2019-02-26 | 中国平安人寿保险股份有限公司 | Data synchronize generation method, device, computer equipment and storage medium |
| CN109814895A (en) * | 2018-11-29 | 2019-05-28 | 广州因特信息科技有限公司 | A kind of database update method and system of automation |
| CN109902078A (en) * | 2019-01-10 | 2019-06-18 | 杭州迪普科技股份有限公司 | Database upgrade compatible method, apparatus, equipment and storage medium |
| CN112181946A (en) * | 2020-09-28 | 2021-01-05 | 云知声智能科技股份有限公司 | Method and device for automatically maintaining dynamic database script |
| CN112817931A (en) * | 2019-11-18 | 2021-05-18 | 大唐移动通信设备有限公司 | Method and device for generating incremental version file |
-
2006
- 2006-11-13 CN CNB200610114522XA patent/CN100570604C/en not_active Expired - Fee Related
Cited By (50)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101859254A (en) * | 2009-04-02 | 2010-10-13 | 国际商业机器公司 | Automatically recommending upgrade approach for customizable software product |
| CN101533356B (en) * | 2009-04-21 | 2013-02-27 | 华为技术有限公司 | A method, a device and a system for realizing software online upgrade |
| CN102096671A (en) * | 2009-12-14 | 2011-06-15 | 深圳速浪数字技术有限公司 | Method and equipment for generating business and operation support system (BOSS) database upgrading script |
| CN101908064A (en) * | 2010-07-20 | 2010-12-08 | 中兴通讯股份有限公司 | Data base backup recovery method and device |
| CN102411588A (en) * | 2010-09-26 | 2012-04-11 | 金蝶软件（中国）有限公司 | Comparison checking method and system of data table |
| CN102065413B (en) * | 2010-11-17 | 2014-03-12 | 北京北方烽火科技有限公司 | Database updating method and system, and base station self-starting method and system |
| CN102065413A (en) * | 2010-11-17 | 2011-05-18 | 北京北方烽火科技有限公司 | Database updating method and system, and base station self-starting method and system |
| US10747735B2 (en) | 2011-09-30 | 2020-08-18 | Emc Corporation | System and method of dynamic data object upgrades |
| US10242044B2 (en) | 2011-09-30 | 2019-03-26 | Emc Corporation | System and method of rolling upgrades of data traits |
| CN103946794B (en) * | 2011-09-30 | 2017-03-29 | Emc 公司 | The system of the rolling upgrade of data characteristicses, apparatus and method |
| US9330122B2 (en) | 2011-09-30 | 2016-05-03 | Emc Corporation | System and method of dynamic data object upgrades |
| CN103946794A (en) * | 2011-09-30 | 2014-07-23 | Emc公司 | Cross-reference and priority claim to related applications |
| US9977799B2 (en) | 2011-09-30 | 2018-05-22 | Emc Corporation | System and method of dynamic data object upgrades |
| CN103294724B (en) * | 2012-03-05 | 2018-11-23 | 百度在线网络技术（北京）有限公司 | A kind of management method and system of database structure |
| CN103294724A (en) * | 2012-03-05 | 2013-09-11 | 百度在线网络技术（北京）有限公司 | Method for managing database structures and system for method |
| CN102902707A (en) * | 2012-08-01 | 2013-01-30 | 杭州华三通信技术有限公司 | Method for realizing compatibility of binary data with different versions and data version converting system |
| CN102902707B (en) * | 2012-08-01 | 2016-03-30 | 杭州华三通信技术有限公司 | The method of different editions binary data compatibility and versions of data converting system |
| CN102890720A (en) * | 2012-10-16 | 2013-01-23 | 南京通达海信息技术有限公司 | Database inspection and maintenance method |
| CN102902818A (en) * | 2012-10-26 | 2013-01-30 | 杭州迪普科技有限公司 | Method and device for upgrading database |
| CN104572644A (en) * | 2013-10-10 | 2015-04-29 | 北京大学 | Database updating device and database updating method |
| CN104572644B (en) * | 2013-10-10 | 2018-05-22 | 北京大学 | Database update device and database update method |
| CN104714957B (en) * | 2013-12-13 | 2018-11-23 | 阿里巴巴集团控股有限公司 | A kind of variation and device of table structure |
| CN104714957A (en) * | 2013-12-13 | 2015-06-17 | 阿里巴巴集团控股有限公司 | List structure changing method and device |
| CN105335436A (en) * | 2014-08-11 | 2016-02-17 | 方正国际软件(北京)有限公司 | Method and equipment for upgrading database structure |
| CN104216948A (en) * | 2014-08-12 | 2014-12-17 | 上海新炬网络技术有限公司 | Difference control method of data model |
| CN104216948B (en) * | 2014-08-12 | 2017-12-05 | 上海新炬网络技术有限公司 | A kind of difference control method of data model |
| CN104750774A (en) * | 2014-12-15 | 2015-07-01 | 北京星网锐捷网络技术有限公司 | Database upgrading method and device |
| CN105989089A (en) * | 2015-02-12 | 2016-10-05 | 阿里巴巴集团控股有限公司 | Data comparison method and device |
| CN106156052A (en) * | 2015-03-27 | 2016-11-23 | 中兴通讯股份有限公司 | Terminal data upgrade method and device |
| CN104881455A (en) * | 2015-05-20 | 2015-09-02 | 深圳市酷开网络科技有限公司 | Structural difference processing method and system based on MYSQL |
| CN104881455B (en) * | 2015-05-20 | 2019-01-29 | 深圳市酷开网络科技有限公司 | A kind of architectural difference processing method and system based on MYSQL |
| CN104951550A (en) * | 2015-06-25 | 2015-09-30 | 走遍世界（北京）信息技术有限公司 | Data storage method and device |
| CN104951550B (en) * | 2015-06-25 | 2018-07-17 | 走遍世界（北京）信息技术有限公司 | Date storage method and device |
| CN105224361B (en) * | 2015-09-15 | 2018-05-25 | 华讯方舟科技有限公司 | A kind of method and system upgraded to sqlite3 type embedded databases |
| CN105224361A (en) * | 2015-09-15 | 2016-01-06 | 深圳市华讯方舟软件信息科技有限公司 | A kind of method and system that sqlite3 type embedded database is upgraded |
| CN108431769A (en) * | 2016-01-21 | 2018-08-21 | 微软技术许可有限责任公司 | The database and service upgrade of no shutdown time |
| CN108431769B (en) * | 2016-01-21 | 2021-09-17 | 微软技术许可有限责任公司 | Database and service upgrade without downtime |
| CN106250485A (en) * | 2016-07-29 | 2016-12-21 | 北京北信源软件股份有限公司 | Database upgrade method, Apparatus and system |
| CN106339500A (en) * | 2016-09-09 | 2017-01-18 | 浪潮软件股份有限公司 | Remote database comparison tool and method |
| CN108023920A (en) * | 2016-10-28 | 2018-05-11 | 阿里巴巴集团控股有限公司 | A kind of data pack transmission method, equipment and application interface |
| CN108023920B (en) * | 2016-10-28 | 2021-11-26 | 阿里巴巴集团控股有限公司 | Data packet transmission method, equipment and application interface |
| CN106777025A (en) * | 2016-12-08 | 2017-05-31 | 北京中电普华信息技术有限公司 | A kind of analysis method and system of database physical model |
| CN108614868A (en) * | 2018-04-16 | 2018-10-02 | 北京酷我科技有限公司 | A kind of database automatically updating method |
| CN109388676A (en) * | 2018-08-21 | 2019-02-26 | 中国平安人寿保险股份有限公司 | Data synchronize generation method, device, computer equipment and storage medium |
| CN109388676B (en) * | 2018-08-21 | 2023-11-14 | 中国平安人寿保险股份有限公司 | Data synchronization generation method, device, computer equipment and storage medium |
| CN109814895A (en) * | 2018-11-29 | 2019-05-28 | 广州因特信息科技有限公司 | A kind of database update method and system of automation |
| CN109902078A (en) * | 2019-01-10 | 2019-06-18 | 杭州迪普科技股份有限公司 | Database upgrade compatible method, apparatus, equipment and storage medium |
| CN112817931A (en) * | 2019-11-18 | 2021-05-18 | 大唐移动通信设备有限公司 | Method and device for generating incremental version file |
| CN112817931B (en) * | 2019-11-18 | 2024-03-29 | 大唐移动通信设备有限公司 | Incremental version file generation method and device |
| CN112181946A (en) * | 2020-09-28 | 2021-01-05 | 云知声智能科技股份有限公司 | Method and device for automatically maintaining dynamic database script |
Also Published As
| Publication number | Publication date |
|---|---|
| CN100570604C (en) | 2009-12-16 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN100570604C (en) | A kind of method of relation data base applications automatic upgrade | |
| US20210004383A1 (en) | System and method for enabling extract transform and load processes in a business intelligence server | |
| US20210117437A1 (en) | Data model transformation | |
| US7310653B2 (en) | Method, system, and product for maintaining software objects during database upgrade | |
| US8141029B2 (en) | Method and system for executing a data integration application using executable units that operate independently of each other | |
| US9411562B2 (en) | Inter-application transform builder for cloud applications | |
| US20090282089A1 (en) | Data migration factory | |
| US20120150919A1 (en) | Agency management system and content management system integration | |
| US20010025287A1 (en) | Document integrated management apparatus and method | |
| US6915313B2 (en) | Deploying predefined data warehouse process models | |
| US7739232B2 (en) | Programming system for occasionally-connected mobile business applications | |
| CN101685395A (en) | Object property processing method of product data management system | |
| CN109117173B (en) | Configuration file management method based on project version development | |
| US8630981B1 (en) | Techniques for differencing binary installation packages | |
| CN115495465A (en) | Data updating method and device and electronic equipment | |
| US8839114B1 (en) | System, method, and computer program for generating a graphical representation of at least a portion of a synchronized network model | |
| KR20090003040A (en) | Method and system of managing data quality through provisioning of metadata in the execution of business process | |
| JP2010128776A (en) | Apparatus and method for automatic maintenance of portable terminal | |
| JP5596517B2 (en) | Internationalized screen generation system and program | |
| CN111984648B (en) | Data initialization method and system under micro-service architecture | |
| CN102611580A (en) | Multi-version network management method based on specification drive | |
| CN115495442B (en) | Database operation file generation method, device, equipment and storage medium | |
| US20200342146A1 (en) | Filtering components compatible with a computer-modeled structure | |
| Zhang et al. | Design of an online teaching and research communication APP based on computer algorithms | |
| CN117851424A (en) | SQL command statement conversion method and device, electronic equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20091216 Termination date: 20151113 |
|
| CF01 | Termination of patent right due to non-payment of annual fee |