CN100426291C - System and method to realize database upgrading in background management system - Google Patents
System and method to realize database upgrading in background management system Download PDFInfo
- Publication number
- CN100426291C CN100426291C CNB2005101018592A CN200510101859A CN100426291C CN 100426291 C CN100426291 C CN 100426291C CN B2005101018592 A CNB2005101018592 A CN B2005101018592A CN 200510101859 A CN200510101859 A CN 200510101859A CN 100426291 C CN100426291 C CN 100426291C
- Authority
- CN
- China
- Prior art keywords
- database
- version
- upgrading
- data
- subsystem
- 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.)
- Active
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/21—Design, administration or maintenance of databases
- G06F16/211—Schema design and management
- G06F16/213—Schema design and management with details for schema evolution support
Abstract
The invention relates to a system to upgrade the database in the background management system that includes: vision recognition subsystem, vision upgrading subsystem and description/knowledge system, the vision recognition subsystem generates and maintains the description/knowledge of various vision databases; the vision upgrading subsystem uses said description/knowledge to upgrade the database; the description/knowledge system consists of several describing files, and is the input of the vision upgrading subsystem, and is the output of the vision recognition subsystem. The invention also relates to a corresponding database upgrading method, it includes: the vision recognition subsystem generates and maintains the steps of description/knowledge of various vision databases, and the vision subsystem uses said description/knowledge to upgrade the database. The invention can be used in the embedded communication system, it can upgrade intelligentizely and automatically, recognize the original vision and the present vision automatically, and the database in the background management system can be upgraded smoothly with the software vision.
Description
Technical field
The present invention relates to a kind of system and method for database upgrade, relate in particular to a kind of system and method for fulfillment database upgrading in background management system.
Background technology
Software product is stopping all there be possibility of edition upgrading before the exploitation fully, and because of various reasons, requirement is upgraded to highest version by lowest version.Generally all be to adopt a kind of like this architecture of AM/BAM in embedded communication system, the foreground is the embedded system main frame, and the backstage is a Win NT/2000 management system, uses relational database and preserve host data in background management system.When the background management system software release upgrade, the database of the respective version that is necessary to upgrade makes things convenient for edition upgrading.
Existing database upgrade is after the background management system software release upgrade is installed, and creates database again, and all need be in background management system client manual configuration again with professional tables of data data relevant or that need to customize.Owing to can not upgrade with the software version corresponding database of background management system thereupon, but will create database again, so the business datum that disposes in the original version lost thereupon also, this has brought a lot of inconvenience for the foreground host data configuration.So there is following shortcoming in prior art:
1. under the more situation of business datum table, reset Configuration Data and to expend great amount of manpower;
2. the configuration data of reduction original version mismatches the rate height, and some tables of data leakiness is joined, thereby has increased the difficulty of development﹠ testing personnel positioning problems;
3. the time cost that spent of resetting Configuration Data is long, is unfavorable for quick customer in response demand;
4. do not accomplish the seamless upgrade of database with backstage management system software version.
Summary of the invention
Technical matters to be solved by this invention is to provide a kind of system and method that is applied to the upgrading of fulfillment database in background management system in the embedded communication system, it can realize intellectuality and automatic updating, do not need the people to participate in, can discern source version and purpose version automatically, the database of realization background management system is smooth upgrade with software release upgrade.
For solving the problems of the technologies described above, the technical solution adopted in the present invention is: the system that a kind of fulfillment database upgrading in background management system is provided, it comprises version recognition subsystem, edition upgrading subsystem and description/knowledge system, the description/knowledge in wherein said version recognition subsystem generation and existing each edition data storehouse of maintenance software; Described edition upgrading subsystem utilizes described description/knowledge that database is upgraded; Described description/knowledge system is made up of some description document, it is the input of edition upgrading subsystem, the output of version recognition subsystem, described description document comprise upgrading SQL script file between DDF, database version description document, database version identification file, database table description document and database version.
Described description document also comprises pre-service SQL script file and aftertreatment SQL script file.
For solving above-mentioned another technical matters, the technical solution adopted in the present invention is: a kind of method of fulfillment database upgrading in background management system is provided, and it may further comprise the steps: the description/knowledge in generation of version recognition subsystem and existing each edition data storehouse of maintenance software; The edition upgrading subsystem utilizes foregoing description/knowledge that database is upgraded, and described version recognition subsystem produces and the description/knowledge in existing each edition data storehouse of maintenance software may further comprise the steps:
A) the version recognition subsystem reads the database information that all need upgrade data from DDF;
B) the version recognition subsystem generates the database version description document;
C) the version recognition subsystem generates database version identification file;
E) the version recognition subsystem generates upgrading SQL script file between database version;
F) the version recognition subsystem generates the database table description document;
Described edition upgrading subsystem utilizes foregoing description/knowledge that database is upgraded and may further comprise the steps:
H) the edition upgrading subsystem reads the database information that all need upgrade data from DDF;
I) the edition upgrading subsystem is from the database version description document, all version informations of reading database;
J) the edition upgrading subsystem is discerned file according to database version, and reading database version feature information is according to the source version and the purpose version of version feature information Recognition database;
L) the edition upgrading subsystem is carried out the upgrading SQL script file between version, adjusts the list structure and the data in edition data storehouse, source;
M) the edition upgrading subsystem reads the importing data mode of all tables from the database table description document, according to importing data mode, the data of each table is imported purpose edition data storehouse by edition data storehouse, source.
Description/the knowledge in described version recognition subsystem generation and existing each edition data storehouse of maintenance software is further comprising the steps of:
G) whether the upgrading relation constitutes directed acyclic graph between the version in the version recognition subsystem inspection database version description document, if constitute directed acyclic graph, then compares difference in version, and the output detailed report if do not constitute, then finishes version identification.
Described step c) and e) between also comprise step d), be whether table in the version recognition subsystem judgment data storehouse exists constraint, if there is constraint, then the version recognition subsystem generates the pre-service SQL script file and the aftertreatment SQL script file of database version, if there is not the then direct execution in step e of constraint).
Further improvement in the technical proposal is: it is further comprising the steps of that described edition upgrading subsystem utilizes foregoing description/knowledge that database is upgraded: k) the edition upgrading subsystem is from the database version description document, upgrading relation between the reading database version is analyzed the shortest upgrading path that obtains from the source version to the purpose version; Described l) step is specially: the edition upgrading subsystem is carried out the upgrading SQL script file between version along the shortest upgrading path from the source version to the purpose version, adjusts the list structure and the data in edition data storehouse, source.
Described step m) further comprise step n), if promptly should have constraint by table, then before importing data, carry out the pre-service SQL script file of this table, after importing data, carry out the aftertreatment SQL script file of this table.
Step k) the shortest upgrading path of described analysis from the source version to the purpose version adopts and asks the directed acyclic graph certain source point to the algorithm of all the other each summit shortest paths.
The invention has the beneficial effects as follows: because the present invention adopts version recognition subsystem, edition upgrading subsystem and description/knowledge system in conjunction with the database upgrade that is implemented in the background management system, therefore it can realize intellectuality and automatic updating, do not need the people to participate in, can discern source version and purpose version automatically, the database of realization background management system is smooth upgrade with software release upgrade, should have good expandability based on the database upgrade method system of describing that makes; In addition, the present invention can be integrated in the mounting disc of Backend Administration Module software, and the upgrading Installation Options is provided, upgrade data when Backend Administration Module software is installed, and the inspection work of most consistance correctness of database upgrade is finished by system, thereby reduces exploitation/maintainer's work; Moreover, because the shortest upgrading path of analysis of the present invention from the source version to the purpose version adopts is to ask the directed acyclic graph certain source point to the algorithm of all the other each summit shortest paths, therefore in the database upgrade process, can determine upgrading path and strategy from the source version to the purpose version, when the lowest version from background management system software was upgraded to highest version, it can be sought a upgrading path the shortest database is upgraded.
Description of drawings
Fig. 1 is the system architecture diagram of the present invention's fulfillment database upgrading in background management system.
Fig. 2 is the version recognition subsystem work synoptic diagram of system shown in Figure 1.
Fig. 3 is the edition upgrading subsystem work synoptic diagram of system shown in Figure 1.
Fig. 4 is that the present invention analyzes the directed acyclic graph that algorithm adopted of source version to the purpose version upgrade path.
Embodiment
See also Fig. 1, the system of the present invention's fulfillment database upgrading in background management system comprises version recognition subsystem, edition upgrading subsystem and description/knowledge system, wherein description/the knowledge in generation of version recognition subsystem and existing each edition data storehouse of maintenance software; The edition upgrading subsystem utilizes foregoing description/knowledge that database is upgraded; Description/knowledge system is made up of some description document, it is the input of edition upgrading subsystem, the output of version recognition subsystem, description document comprises: upgrading SQL script file between DDF, database version description document, database version identification file, pre-service SQL script file, aftertreatment SQL script file, database table description document and database version.Wherein:
1) DDF
General introduction: describe the data of database that to upgrade in the escalation process.Whole edition upgrading system just uses this DDF.
2) database version description document
General introduction: all versions of descriptive data base and the relation of the upgrading between version.Each database that will upgrade has this database version description document.
3) database version identification file
General introduction: preserve the database information of this version, comprise all table information in the database,, be used to discern each version as list structure definition (essential, all tables), field implication (optional, host service table), field enumerated value implication (optional, host service table).Each version of database has this database version identification file.
4) pre-service SQL script file
General introduction: pre-service SQL script file is divided into: database pre-service SQL script file, table pre-service SQL script file.Each database of each version has a database pre-service SQL script file at most, and it is carried out before database imports data, and any special processing that need carry out before database imports data can be write the SQL script in this document.Each table of each database of each version has a table pre-service SQL script file at most, and it is carried out before importing these table data, and any special processing that need carry out before importing these table data can be write the SQL script in this document.
5) aftertreatment SQL script file
General introduction: aftertreatment SQL script file is divided into: database aftertreatment SQL script file, table aftertreatment SQL script file.Each database of each version has a database aftertreatment SQL script file at most, and it is carried out after database imports data, and any special processing that need carry out after database imports data can be write the SQL script in this document.Each table of each database of each version has a table aftertreatment SQL script file at most, and it is carried out after importing these table data, and any special processing that need carry out after these table data of importing can be write the SQL script in this document.
6) upgrading SQL script file between database version
General introduction: be used to write the upgrade script that the relative source of purpose version version changes.If the relative source of purpose version version has increased table, should write the script of establishment table.If the relative source of purpose version version has reduced table, should write the script of delete list.If between two versions, certain list structure (comprising Field Definition, the enumerated value definition) changes, and should write upgrade script for it, is responsible for adjustment form structure and data, makes it consistent with redaction.
7) database table description document
General introduction: describe in the escalation process importing data mode of all tables in the database.Each database that will upgrade has this database table description document.
Table in the database roughly is divided into: a, the default data is arranged, can not revise/delete the default data or increase new data; B, the default data is arranged, can not revise/delete the default data but may increase new data; C, the default data is arranged, may revise/delete the default data but can not increase new data; D, the default data is arranged, may revise/delete the default data or increase new data; E, do not have the default data, may increase new data.Correspondingly, the importing data mode is divided into: the 0 (default data that keeps redaction fully, be fit to type a), 1 (imports the data in the early version fully, be fit to type d and e), 2 (self-defined SQL script mode relatively flexibly, can be fit to type b and C and special circumstances that some may also not considered).
The method of the present invention's fulfillment database upgrading in background management system comprises that the version recognition subsystem produces and the step of the description/knowledge in existing each edition data storehouse of maintenance software and the step that the edition upgrading subsystem utilizes foregoing description/knowledge that database is upgraded.
See also Fig. 2, the version recognition subsystem of the present invention system of fulfillment database upgrading in background management system is output with description/knowledge system, correctness, the consistance being responsible for generating description document and checking description document.The version recognition subsystem produces and the description/knowledge in existing each edition data storehouse of maintenance software may further comprise the steps:
A) the version recognition subsystem reads the database information that all need upgrade data from DDF;
B) the version recognition subsystem generates the database version description document;
C) the version recognition subsystem generates database version identification file;
D) whether the table in the version recognition subsystem judgment data storehouse exists constraint, and as if there being constraint, then the version recognition subsystem generates the pre-service SQL script file and the aftertreatment SQL script file of database version, if there is not the then direct execution in step e of constraint);
E) the version recognition subsystem generates upgrading SQL script file between database version;
F) the version recognition subsystem generates the database table description document;
G) whether the upgrading relation constitutes directed acyclic graph between the version in the version recognition subsystem inspection database version description document, if constitute directed acyclic graph, then compares difference in version, and the output detailed report if do not constitute, then finishes version identification.
See also Fig. 3, the description document that the edition upgrading subsystem of the present invention system of fulfillment database upgrading in background management system utilizes the version recognition subsystem to generate is upgraded to database, and the edition upgrading subsystem utilizes foregoing description/knowledge that database is upgraded and may further comprise the steps:
H) the edition upgrading subsystem reads the database information that all need upgrade data from DDF;
I) the edition upgrading subsystem is from the database version description document, all version informations of reading database;
J) the edition upgrading subsystem is discerned file according to database version, and reading database version feature information is according to the source version and the purpose version of version feature information Recognition database;
K) the edition upgrading subsystem is from the database version description document, and the upgrading relation between the reading database version is analyzed the shortest upgrading path that obtains from the source version to the purpose version;
L) the edition upgrading subsystem is carried out the upgrading SQL script file between version along the shortest upgrading path from the source version to the purpose version, adjusts the list structure and the data in edition data storehouse, source;
M) the edition upgrading subsystem is from the database table description document, read the importing data mode of all tables, according to importing data mode, the data of each table are imported purpose edition data storehouse by edition data storehouse, source, if should have constraint by table, then before importing data, carry out the pre-service SQL script file of this table, after importing data, carry out the aftertreatment SQL script file of this table.
Step k wherein) the shortest upgrading path of described analysis from the source version to the purpose version adopts and asks the directed acyclic graph certain source point to the algorithm of all the other each summit shortest paths.Seeing also Fig. 4, is directed acyclic graph of the present invention, and wherein V1, V2, V3, V4, V5, V6 constitute the version of existing software.Vi (i=1,2,3, the 4...) vertex set in the formation directed acyclic graph.Representing can be upgraded to another version from a version with oriented arc connection between the summit, according to the description in the technical scheme, promptly is to have the upgrading relation between two versions.For example, be upgraded to V6 from version V1 following several upgrading pathes arranged:
1)V1?V2?V3?V4?V5?V6
2)V1?V2?V3?V5?V6
3)V1?V2?V3?V6
4)V1?V3?V4?V5?V6
5)V1?V3?V5?V6
6)V1?V3?V6
Can analyze shortest path according to above-mentioned directed acyclic graph shortest path first is V1 V3 V6, is the shortest path that database version V1 is upgraded to V6.
Claims (15)
1, a kind of system of fulfillment database upgrading in background management system, it is characterized in that: it comprises version recognition subsystem, edition upgrading subsystem and description/knowledge system, the description/knowledge in wherein said version recognition subsystem generation and existing each edition data storehouse of maintenance software; Described edition upgrading subsystem utilizes described description/knowledge that database is upgraded; Described description/knowledge system is made up of some description document, it is the input of edition upgrading subsystem, the output of version recognition subsystem, described description document comprise upgrading SQL script file between DDF, database version description document, database version identification file, database table description document and database version.
2. the system of fulfillment database upgrading in background management system as claimed in claim 1, it is characterized in that: described description document also comprises pre-service SQL script file and aftertreatment SQL script file.
3. the system of fulfillment database upgrading in background management system as claimed in claim 2, it is characterized in that: described pre-service SQL script file comprises database pre-service SQL script file and table pre-service SQL script file, each database of each version has this database pre-service SQL script file at most, it is carried out before database imports data, the any special processing that need before database imports data, carry out, can in this document, write the SQL script, each table of each database of each version has a table pre-service SQL script file at most, it is carried out before importing these table data, the any special processing that need carry out before importing these table data can be write the SQL script in this document.
4. the system of fulfillment database upgrading in background management system as claimed in claim 2, it is characterized in that: described aftertreatment SQL script file comprises database aftertreatment SQL script file and table aftertreatment SQL script file, each database of each version has a database aftertreatment SQL script file at most, it is carried out after database imports data, the any special processing that need after database imports data, carry out, can in this document, write the SQL script, each table of each database of each version has a table aftertreatment SQL script file at most, it is carried out after importing these table data, the any special processing that need carry out after these table data of importing can be write the SQL script in this document.
5. the system of fulfillment database upgrading in background management system as claimed in claim 1, it is characterized in that: described DDF is used to describe the data of database that escalation process will be upgraded, this DDF of whole edition upgrading system's use.
6. the system of fulfillment database upgrading in background management system as claimed in claim 1, it is characterized in that: described database version description document is used for all versions and the relation of the upgrading between version of descriptive data base, and each database that will upgrade has this database version description document.
7. the system of fulfillment database upgrading in background management system as claimed in claim 1, it is characterized in that: described database version identification file is used to preserve the database information of this version, comprise all table information in the database, each version of database has this database version identification file.
8. the system of fulfillment database upgrading in background management system as claimed in claim 1 is characterized in that: upgrading SQL script file is used to write the upgrade script that the relative source of purpose version version changes between described database version.
9. the system of fulfillment database upgrading in background management system as claimed in claim 1, it is characterized in that: described database table description document is used for describing escalation process, the importing data mode of all tables in the database, each database that will upgrade have this database table description document.
10. the method for a fulfillment database upgrading in background management system is characterized in that may further comprise the steps:
Description/the knowledge in generation of version recognition subsystem and existing each edition data storehouse of maintenance software;
The edition upgrading subsystem utilizes foregoing description/knowledge that database is upgraded;
Described version recognition subsystem produces and the description/knowledge in existing each edition data storehouse of maintenance software may further comprise the steps:
A) the version recognition subsystem reads the database information that all need upgrade data from DDF;
B) the version recognition subsystem generates the database version description document;
C) the version recognition subsystem generates database version identification file;
E) the version recognition subsystem generates upgrading SQL script file between database version;
F) the version recognition subsystem generates the database table description document;
Described edition upgrading subsystem utilizes foregoing description/knowledge that database is upgraded and may further comprise the steps:
H) the edition upgrading subsystem reads the database information that all need upgrade data from DDF;
I) the edition upgrading subsystem is from the database version description document, all version informations of reading database;
J) the edition upgrading subsystem is discerned file according to database version, and reading database version feature information is according to the source version and the purpose version of version feature information Recognition database;
L) the edition upgrading subsystem is carried out the upgrading SQL script file between version, adjusts the list structure and the data in edition data storehouse, source;
M) the edition upgrading subsystem reads the importing data mode of all tables from the database table description document, according to importing data mode, the data of each table is imported purpose edition data storehouse by edition data storehouse, source.
11. the method for fulfillment database upgrading in background management system as claimed in claim 10 is characterized in that: the description/knowledge in described version recognition subsystem generation and existing each edition data storehouse of maintenance software is further comprising the steps of:
G) whether the upgrading relation constitutes directed acyclic graph between the version in the version recognition subsystem inspection database version description document, if constitute directed acyclic graph, then compares difference in version, and the output detailed report if do not constitute, then finishes version identification.
12. the method for fulfillment database upgrading in background management system as claimed in claim 11, it is characterized in that: described step c) and e) between also comprise step d), be whether table in the version recognition subsystem judgment data storehouse exists constraint, if there is constraint, then the version recognition subsystem generates the pre-service SQL script file and the aftertreatment SQL script file of database version, if there is not the then direct execution in step e of constraint).
13. the method for fulfillment database upgrading in background management system as claimed in claim 10, it is characterized in that: it is further comprising the steps of that described edition upgrading subsystem utilizes foregoing description/knowledge that database is upgraded:
K) the edition upgrading subsystem is from the database version description document, and the upgrading relation between the reading database version is analyzed the shortest upgrading path that obtains from the source version to the purpose version;
Described step 1) is specially: the edition upgrading subsystem is carried out the upgrading SQL script file between version along the shortest described upgrading path from the source version to the purpose version, adjusts the list structure and the data in edition data storehouse, source.
14. the method for fulfillment database upgrading in background management system as claimed in claim 13, it is characterized in that: described step m) further comprise step n), if promptly should have constraint by table, then before importing data, carry out the pre-service SQL script file of this table, after importing data, carry out the aftertreatment SQL script file of this table.
15. the method for fulfillment database upgrading in background management system as claimed in claim 13 is characterized in that: step k) the shortest upgrading path of described analysis from the source version to the purpose version adopts and asks the directed acyclic graph certain source point to the algorithm of all the other each summit shortest paths.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNB2005101018592A CN100426291C (en) | 2005-11-26 | 2005-11-26 | System and method to realize database upgrading in background management system |
| PCT/CN2006/003103 WO2007059698A1 (en) | 2005-11-26 | 2006-11-17 | System and method for realizing database upgrading in background management system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNB2005101018592A CN100426291C (en) | 2005-11-26 | 2005-11-26 | System and method to realize database upgrading in background management system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN1971556A CN1971556A (en) | 2007-05-30 |
| CN100426291C true CN100426291C (en) | 2008-10-15 |
Family
ID=38066916
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CNB2005101018592A Active CN100426291C (en) | 2005-11-26 | 2005-11-26 | System and method to realize database upgrading in background management system |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN100426291C (en) |
| WO (1) | WO2007059698A1 (en) |
Families Citing this family (14)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102025548B (en) * | 2010-12-20 | 2014-12-10 | 中兴通讯股份有限公司 | Multi-version smooth upgrading method and device for user-defined performance indexes |
| CN103019660A (en) * | 2011-09-20 | 2013-04-03 | 佳都新太科技股份有限公司 | Realization of web application data source delay binding |
| CN103324716B (en) * | 2013-06-25 | 2016-08-10 | 四川九洲电器集团有限责任公司 | A kind of application database update method based on Android system |
| CN104572644B (en) * | 2013-10-10 | 2018-05-22 | 北京大学 | Database update device and database update method |
| CN103810100A (en) * | 2013-12-02 | 2014-05-21 | 中标软件有限公司 | Software evolutionary trend analysis system and method |
| CN104881455B (en) * | 2015-05-20 | 2019-01-29 | 深圳市酷开网络科技有限公司 | A kind of architectural difference processing method and system based on MYSQL |
| CN106325902B (en) * | 2015-06-24 | 2020-09-15 | 中兴通讯股份有限公司 | Database software upgrade detection method and device |
| CN106599167B (en) * | 2016-12-09 | 2020-11-20 | 苏州浪潮智能科技有限公司 | System and method for supporting increment updating of database |
| CN108268275B (en) * | 2017-06-12 | 2021-05-04 | 平安普惠企业管理有限公司 | Software version control method and software version control equipment |
| CN107357907A (en) * | 2017-07-17 | 2017-11-17 | 郑州云海信息技术有限公司 | A kind of database upgrade method and device for supporting cross-version |
| CN107861737A (en) * | 2017-11-06 | 2018-03-30 | 国云科技股份有限公司 | A kind of database version moving method of large scale system |
| CN110865829B (en) * | 2018-08-28 | 2024-04-16 | 京东科技控股股份有限公司 | Database upgrading method, system, equipment and storage medium |
| CN110618829B (en) * | 2019-09-20 | 2023-04-28 | 中国银行股份有限公司 | Service data checking method and system for upgrading database system |
| CN111506779B (en) * | 2020-04-20 | 2021-03-16 | 东云睿连(武汉)计算技术有限公司 | Object version and associated information management method and system facing data processing |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1581165A (en) * | 2004-05-18 | 2005-02-16 | 中兴通讯股份有限公司 | Method for realizing relation-database automatic upgrading in communication apparatus |
| WO2005029332A1 (en) * | 2003-09-24 | 2005-03-31 | Sony Corporation | Database schemer update method |
| US20050198630A1 (en) * | 2004-03-08 | 2005-09-08 | Microsoft Corporation | Relational database schema version management |
| CN1713154A (en) * | 2004-06-22 | 2005-12-28 | 中兴通讯股份有限公司 | Method for upgrading network management system in mobile communication |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JPH09130426A (en) * | 1995-11-06 | 1997-05-16 | Nippon Telegr & Teleph Corp <Ntt> | Information providing system |
-
2005
- 2005-11-26 CN CNB2005101018592A patent/CN100426291C/en active Active
-
2006
- 2006-11-17 WO PCT/CN2006/003103 patent/WO2007059698A1/en active Application Filing
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2005029332A1 (en) * | 2003-09-24 | 2005-03-31 | Sony Corporation | Database schemer update method |
| US20050198630A1 (en) * | 2004-03-08 | 2005-09-08 | Microsoft Corporation | Relational database schema version management |
| CN1581165A (en) * | 2004-05-18 | 2005-02-16 | 中兴通讯股份有限公司 | Method for realizing relation-database automatic upgrading in communication apparatus |
| CN1713154A (en) * | 2004-06-22 | 2005-12-28 | 中兴通讯股份有限公司 | Method for upgrading network management system in mobile communication |
Non-Patent Citations (2)
| Title |
|---|
| 基于Oracle的管理信息系统数据库自动升级方法研究及实现. 彭贤海，全国庆，张健.计算机工程与应用. 2004 |
| 基于Oracle的管理信息系统数据库自动升级方法研究及实现. 彭贤海，全国庆，张健.计算机工程与应用. 2004 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN1971556A (en) | 2007-05-30 |
| WO2007059698A1 (en) | 2007-05-31 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN100426291C (en) | System and method to realize database upgrading in background management system | |
| CN103365683B (en) | For end-to-end patch automation and integrated method and system | |
| US9372784B2 (en) | Test system configuration method and system | |
| CN106649771B (en) | The data model update method and system of database | |
| US9075695B2 (en) | Version conflict checking to installable unit | |
| CN1968154A (en) | System and method for service expansion using plug | |
| ITTO980720A1 (en) | PROCEDURE FOR INSTALLING AND VERIFYING THE SOFTWARE FOR A CUSTOM MADE COMPUTER SYSTEM. | |
| US20080052308A1 (en) | Method and system for realizing automatic adaptation of data object model | |
| ITTO980722A1 (en) | PROCEDURE FOR INSTALLING AND / OR VERIFYING THE SOFTWARE FOR A COMPUTER SYSTEM MADE TO ORDER, AND COMPUTER SYSTEM FOR | |
| US20080010535A1 (en) | Automated and configurable system for tests to be picked up and executed | |
| CN105446868A (en) | System compatibility testing method, test case management method and related devices | |
| CN100556211C (en) | A kind of upgrade method of mobile communication network management system | |
| CN104915262A (en) | Calibration system and method based on EXCEL data structure | |
| CN105512017A (en) | Database compatibility detection method and device | |
| CN110032594B (en) | Customizable data extraction method and device for multi-source database and storage medium | |
| CN111737140A (en) | Interface automation test method, device, equipment and computer readable storage medium | |
| CN113515297B (en) | Version updating method and device, electronic equipment and storage medium | |
| CN115712623A (en) | Batch data fault-tolerant acquisition method based on capture metadata change | |
| US20030158767A1 (en) | Method and system for adaptive software system interface and external database synchronization | |
| CN114895955A (en) | Method, device and equipment for controlling metadata version of low-code platform | |
| CN104881455B (en) | A kind of architectural difference processing method and system based on MYSQL | |
| CN107783870A (en) | A kind of server-compatible test result management method and system | |
| US6785361B1 (en) | System and method for performance measurement quality assurance | |
| WO2005114396A3 (en) | Reporting module definition language system and method | |
| CN105809495A (en) | Billing system dependent on background non-independent interface and method for billing system |
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 | ||
| TR01 | Transfer of patent right |
Effective date of registration: 20201211 Address after: 225722 private road, Liuji village, Zhangguo Town, Xinghua City, Taizhou City, Jiangsu Province Patentee after: Jiangsu Zhaoyang heating and Cooling Technology Co.,Ltd. Address before: Unit 2414-2416, main building, no.371, Wushan Road, Tianhe District, Guangzhou City, Guangdong Province Patentee before: GUANGDONG GAOHANG INTELLECTUAL PROPERTY OPERATION Co.,Ltd. Effective date of registration: 20201211 Address after: Unit 2414-2416, main building, no.371, Wushan Road, Tianhe District, Guangzhou City, Guangdong Province Patentee after: GUANGDONG GAOHANG INTELLECTUAL PROPERTY OPERATION Co.,Ltd. Address before: 518129 Bantian HUAWEI headquarters office building, Longgang District, Guangdong, Shenzhen Patentee before: HUAWEI TECHNOLOGIES Co.,Ltd. |
|
| TR01 | Transfer of patent right |