CN1547118A - Synchronous configuration copying method based on MS SQL Server - Google Patents
Synchronous configuration copying method based on MS SQL Server Download PDFInfo
- Publication number
- CN1547118A CN1547118A CNA2004100370359A CN200410037035A CN1547118A CN 1547118 A CN1547118 A CN 1547118A CN A2004100370359 A CNA2004100370359 A CN A2004100370359A CN 200410037035 A CN200410037035 A CN 200410037035A CN 1547118 A CN1547118 A CN 1547118A
- Authority
- CN
- China
- Prior art keywords
- server
- database
- select
- subscriber
- issue
- 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)
Abstract
The present invention discloses a synchronous configuration copying method based on MS SQL Server. By invoking the SQL-DMO API interface provided by the MS SQL Server database system, in combination with the module packaging technique, the process executes internal encapsulation and manipulation simplifying for the operation steps for the synchronous configuration copying to realize the automatic allocation functions of data-base synchronization copying. According to the process, the synchronous configuration copying course is completed through four steps as follows: a) selecting and connecting a publishing server; b) creating a publishing; c) selecting and connecting a subscription server; d) creating a subscription. Compared with the process for executing allocation through the graphical user interface of the MS SQL Server database and the executing acting edition, said process in accordance with the present invention possesses obvious advantages as follows: 1) the synchronous configuration copying process is simple; 2) the maintenance cost is reduced; 3) the adaptability is improved.
Description
Technical field
The present invention relates to MS SQL Server data bank network synchronous applications field, relate in particular to a kind of synchronization replication collocation method based on MS SQL Server.
Background technology
Synchronization replication is Premium Features of data base management system (DBMS) (DBMS), the Distributed Application of database is played a part crucial, therefore receives much attention, and is used widely; But in use, build, the configuration synchronization copying surroundings is the difficult problem that industry is generally acknowledged always.The synchronization replication collocation method that uses has two kinds at present:
(1) graphic user interface that provides by data base management system (DBMS) (DBMS) is finished by hand
Layoutprocedure;
(2) by carrying out database script, finish layoutprocedure;
But, no matter be by the graphic user interface of database or by carrying out the method that script is configured, very big defective is all arranged:
(1) the graphical interfaces configuration mode of database, collocation method is manual type fully, configuration step is multiple
Assorted, general technical attendant can't be competent at all, particularly in the database table number very
Under many situations, carry out the synchronization replication configuration, be very easy to make mistakes according to database table.
(2) carry out the synchronization replication configuration by database figure interface, need undoubtedly the maintainer is carried out specially
The industry training, maintenance cost is very high.
(3) the synchronization replication configuration script of database only could be given birth to after finishing artificial synchronous replicated setup
Become, and dirigibility has considerable restraint, in case the installation site of database, participate in multiple synchronously
The database server title of system changes, and just needs manual amendment's script, just can carry out together
The step replicated setup, and not only loaded down with trivial details but also make mistakes easily.
MS SQL Server database provides SQL-DMO (data management object) DLL (dynamic link library) since 7.0 versions, can simplify the synchronization replication step by the SQL-DMO interface, realizes the automatic configuration feature of synchronization replication.
Summary of the invention
The objective of the invention is to overcome the defective of above-mentioned prior art, a kind of very simple synchronization replication collocation method is provided.The present invention has following characteristics: 1) the synchronization replication layoutprocedure is simple, is finished automatically by system basically, and is less demanding to maintainer's technical merit, only needs its ABC of understanding synchronization replication to get final product; 2) only need simple help file, operation instructions, can finish the synchronization replication configuration, greatly reduced maintenance cost, the efficient of synchronization replication configuration simultaneously improves greatly; 3) with respect to the database script configuration mode, better adaptability of the present invention after server name or the change of database installation site, does not need the present invention is done any change.
Technical scheme of the present invention is as follows:
A kind of synchronization replication collocation method based on MS SQL Server, it is characterized in that: call the SQL-DMO api interface that MS SQLServer Database Systems provide, the operation steps that the database synchronization replication is disposed encapsulates, and described synchronization replication collocation method comprises four management objects at least: selection also connects publisher server management object, establishment release management object, selection Subscriber management object, establishment subscription management object; Described synchronization replication collocation method may further comprise the steps:
A) selection and connection publisher server;
B) create issue, this step comprises a series of layoutprocedures of being finished automatically by Database Systems;
C) selection and connection Subscriber;
D) create subscription, this step comprises a series of layoutprocedures of being finished automatically by Database Systems.
Described method, wherein said step a) provides external user interface, by user's input, selects the publisher server title.
Described method, wherein said step c) provides external user interface, by user's input, selects the Subscriber title.
Described method, the selection of wherein said step a) and connection publisher server may further comprise the steps:
A1) execution environment of initialization DMO;
A2) the database server information of inquiry and registration to the local computer;
A3) select publisher server, account number and password;
A4) judge whether selecteed server is registered in group of server,, then directly hold if registered
Whether successful connection is verified in the bind command of line data storehouse, if selecteed server is not in service
Register in the device group, then at first register operation, after succeeding in registration, carry out database again and connect
Order, and publisher server information is saved in the global variable.
Described method, the establishment issue of wherein said step b) may further comprise the steps:
B1) at first from global variable, obtain the publisher server title, Distributor is set then;
B2) position of specifying snapshot document to press from both sides;
B3) enable publisher server, from global variable, obtain the publisher server title;
B4) select publication database;
B5) select the issue type, select the merge replication type;
B6) given subscription type of server;
B7) select the issue project;
B8) select issue to describe;
B9) self-defined issue attribute;
B10) start snapshot agent, initialization issue behind the startup snapshot agent.
A following group selection value is arranged described method, the sequence of steps b1 that wherein said step b) comprises)～b10):
B11) at step b1) in, it is the default selection of system database that Distributor is set, i.e. the distribution clothes
Affair device and publisher server are same server;
B21) at step b2) in, specifying the position of snapshot document folder is the default selection of database;
B41) at step b4) in, database to be released predefined is good;
B51) at step b5) in, predefined is good for the issue type;
B61) at step b6) in, the given subscription type of server is MS SQL Server database service
Device;
B81) at step b8) in, select default value not describe for having;
B91) at step b9) in, select database table is carried out by row, filters or do not filter by row; Described method, the selection of wherein said step c) and connection Subscriber may further comprise the steps:
C1) select Subscriber, account number and password;
C2) judge whether selecteed server is registered in group of server,, then directly hold if registered
Whether successful connection is verified in the bind command of line data storehouse, if selecteed server is not at clothes
Register in the affair device group, then at first register operation, after succeeding in registration, carry out database again and connect
Connect order and Subscriber information is saved in the global variable.
Described method, the establishment of wherein said step d) is subscribed to and be may further comprise the steps:
D1) Subscriber is set;
D2) select destination data storehouse, i.e. subscription database;
D3) scheduling of merging Agent is set; Merging Agent uses with merge replication; Merge
Agent is used initial snapshot on Subscriber, and moves and regulate the establishment initial snapshot
The incremental data change that takes place afterwards; Each merges subscribes to the merging Agent that oneself is all arranged,
This merges the agency and connects publisher server and Subscriber simultaneously and they are upgraded;
D4) after finishing the initialization issue, initialization is subscribed to;
D5) subscription priority being set is the database default value;
D6) start the Agent service, revise the scheduling that operation is acted on behalf of in merging.
Described method, wherein: described selection and connection publisher server management object are the CConnPublisher class, described establishment release management object is the CCreatePublication class, described selection Subscriber management object is the CConnSubscriber class, and described establishment subscription management object is the CCreateSubscription class.
The invention provides the synchronous implementation method of a kind of advantages of simplicity and high efficiency configuration database, compare with the script configuration mode, have clear superiority in the following areas with the graphical interfaces configuration mode of database itself:
1) the graphical interfaces configuration mode that carries of database is the human configuration mode fully, and the present invention is auto configuration mode substantially, thus the complexity of configuration obviously reduce, not high to the technical requirement of technical attendant.And when being configured by the graphical interfaces that database carries, need understand in depth configuration step and synchronization principles, just can finish configuration, this mode configuration step is many in addition, more loaded down with trivial details, particularly under the many situations of the table of synchronization replication, be very easy to make mistakes.
Substantially do not need technical attendant is giveed training when 2) using the present invention to carry out the synchronization replication configuration, only need provide simple help operation instructions to get final product, and the graphical interfaces configuration mode that uses database to carry, need carry out professional training to the maintainer, so the present invention can reduce maintenance cost greatly.
3) function that the invention provides external user interface and search the installation directory of database automatically, layoutprocedure does not rely on the particular location and the database installation site of server, so ratio comes configuration synchronization to be replicated in dirigibility by database script and the adaptability aspect improves greatly.
Description of drawings
Fig. 1 is based on the synchronization replication collocation method schematic flow sheet of MS SQL Server;
Fig. 2 is the schematic flow sheet that the present invention selected and connected publisher server;
Fig. 3 is the schematic flow sheet that the present invention creates issue;
Fig. 4 is the schematic flow sheet that the present invention selected and connected Subscriber;
Fig. 5 is the schematic flow sheet that the present invention creates subscription.
Embodiment
Below in conjunction with accompanying drawing specific embodiments of the invention are described in further detail:
At first, term used herein is carried out lexical or textual analysis:
Publisher server: be the server at the data source place that will duplicate, publisher server is each database table or other database object definition project that will use as copy source.
Issue: be the set of the one or more projects in the database, the grouping of this a plurality of projects make to be specified one group of relevant data of logic and database object duplicate together and is become easier.
Subscriber: be the server that receives the publisher server copy data, the Subscriber definition is to the subscription of particular delivery.
Subscribe to: be request to the duplicate of data or database object, the issue that the subscription definition will receive and time, the place of reception.
Distributor: be with project when publisher server moves to Subscriber, carry out the server of various different tasks, actual carrying out of task depends on performed copy type.
Subscription database: be the database on the Subscriber, it is the database object that will be replicated.
Issue project: be the table for the treatment of synchronization replication, be defined in the ready chained list.
Accompanying drawing 1 has been introduced the main flow process based on the synchronization replication collocation method of MS SQL Server.The present invention is reduced to following four steps with the synchronization replication layoutprocedure of database:
Step 1: select and the connection publisher server;
Step 2: create issue;
Step 3: select and the connection Subscriber;
Step 4: create and subscribe to.
Accompanying drawing 2 has been introduced the present invention's selection and has been connected the flow process of publisher server.
Concrete steps are as follows:
The execution environment of initialization DMO at first, the database server information of inquiry and registration to the local computer then, then select publisher server, account number and password, judge whether selecteed server is registered in group of server, if it is registered, then directly carry out the database bind command, verify whether successful connection, if selecteed server is not registered in group of server, then at first register operation, after succeeding in registration, carry out the database bind command again and publisher server information is saved in the global variable.Only after the publisher server successful connection, just can enter next step layoutprocedure.
Accompanying drawing 3 has been introduced the flow process that the present invention creates issue.
Concrete steps are as follows:
B1) at first from global variable, obtain the publisher server title, Distributor is set then, divide
Sending out server is the default selection of system database, and promptly Distributor and publisher server are same clothes
The affair device;
B2) position of specifying snapshot document to press from both sides is the default selection of database;
B3) enable publisher server, from global variable, obtain the publisher server title;
B4) select publication database, database to be released predefined is good;
B5) select the issue type, predefined is good for the issue type, selects the merge replication type;
B6) the given subscription type of server is a MS SQL Server database server;
B7) select the issue project;
B8) select issue to describe, do not default to and describe;
B9) self-defined issue attribute can be selected database table is carried out by row, by being listed as filtration or not advancing
Row filters;
B10) start snapshot agent, initialization issue behind the startup snapshot agent.
Snapshot agent will use with all copy type.It will prepare publishing table and the framework of storing process and initial data file, storage snapshot document, and the data of relevant initial synchronisation are inserted in the distribution database.
Accompanying drawing 4 has been introduced the present invention's selection and has been connected the flow process of Subscriber.
Concrete steps are as follows:
C1) select Subscriber, account number and password;
C2) judge whether selecteed server is registered in group of server, if it is registered, then directly carry out the database bind command, verify whether successful connection, if selecteed server is not registered in group of server, then at first register operation, after succeeding in registration, carry out the database bind command again and Subscriber information is saved in the global variable.Only after the Subscriber successful connection, just can enter next step layoutprocedure.
Accompanying drawing 5 has been introduced the flow process that the present invention creates subscription.
Concrete steps are as follows:
D1) Subscriber is set;
D2) select destination data storehouse, i.e. subscription database;
D3) scheduling of merging Agent is set; Merging Agent uses with merge replication; Merge
Agent is used initial snapshot on Subscriber, and moves and regulate the establishment initial snapshot
The incremental data change that takes place afterwards; Each merges subscribes to the merging Agent that oneself is all arranged,
This merges the agency and connects publisher server and Subscriber simultaneously and they are upgraded;
D4) after finishing the initialization issue, initialization is subscribed to;
D5) subscription priority being set is the database default value;
D6) start the Agent service, revise the scheduling that operation is acted on behalf of in merging.
C Plus Plus of the present invention is realized, be may further comprise the steps:
1) initialization DMO running environment: call function CoInitialize (), the input parameter value is
NULL；
2) create the DMO object instance: the CreateInstance () function of allocating object, the function form is:
Pointer to object.CreateInstance (_ uuidof (object type));
21) create database application object (Application):
Definition spApplication is _ pointer of ApplicationPtr type call function:
spApplication.CreateInstance(_uuidof(Application)；
22) create distribution database object (DistributionDatabase):
Definition spDistributionDatabase is the finger of DistributionDatabasePtr type
Pin, call function:
spDistributionDatabase.CreateInstance(_uuidof(DistributionDatabase)；
3) registrar information: the count that at first calls the Application object obtains the server number, creates the RegisteredSubscriber object instance then, travels through each server again, obtains server info;
4) registrar: at first call the CreateInstance method and create object instance RegisteredServer, call method PutName, the method PutLogin of RegisteredServer, title, account number and the password that method PutPassword is provided with server then respectively, the Add method of calling the Application object then increases server registration;
5) Connection Service device: at first call the CreateInstance method and create object instance SQLServer, the method PutLoginTimeout, the method Connect that call the SQLServer object then respectively carry out database and connect;
6) Distributor is set: at first the attribute Distributor of allocating object SQLServer appointment master server is a Distributor, the method PutName that calls distribution database object DistributionDatabase then is provided with the distributing data library name, next call the method PutSecurityMode of DistributionDatabase object more respectively, method PutStandardLogin, method PutStandardPassword is provided with the safe mode of distribution database, account number, password calls the method Add of DMO object Distributor at last respectively successively, method PutDistributionServer, method Install finishes the interpolation distribution database respectively, the Distributor title is set and Distributor is installed;
7) publisher server is set: the method PutName that at first calls DMO object DistributionPublisher is provided with the publisher server title, call method PutDistributionDatabase specifies the distribution database that is connected then, call method PutDistributionWorkingDirectory successively again, method PutTrustedDistributorConnection, method PutSecurityMode, method PutThirdParty is provided with working directory, whether trust in succession, safe mode, the method Add that calls DMO object Distributor at last adds publisher server;
8) create the merge replication object: at first the method Item of allocating object SQLServer specifies the title of publication database, the attribute EnableMergePublishing that DMO object ReplicationDatabase is set then is true (TRUE), method PutName, the method PutPublicationAttributes, the method Add that call DMO object MergePublication more successively are provided with the issue title, the method for synchronization are set, promptly push away or draw mode, the method Add of last allocating object ReplicationDatabase adds object MergePublication;
9) select the issue project: the method CreateInstance that at first calls DMO object MergeArticle creates the MergeArticle example, call the method PutName of MergeArticle object then successively, method PutSourceObjectName, method PutSourceObjectOwner, method PutArticleType, method PutPreCreationMethod, method PutColumnTracking, method PutStatus is provided with the publication title, the publication table name is set to be claimed, set out the copyright limit, the publication type is set, initialization mode is set, state of activation, the method Add of last allocating object MergePublication adds object MergeArticle;
10) startup of snapshot agent and stopping: creating object instance Job, method Start, the Stop method of calling the Job object respectively finished the startup of snapshot agent and stopped;
11) Subscriber is set: at first create DMO object instance RegisteredSubscriber, the method PutName of allocating object RegisteredSubscriber, method PutType are provided with the Subscriber title, the subscription type are set successively then, and the method Add of last allocating object Publisher adds object RegisteredSubscriber;
12) create subscription: at first create object instance MergeSubscription, the method PutSubscriber of allocating object MergeSubscription, method PutSubscriptionDB, method PutSyncType, PutPriority, PutStatus realize that Subscriber is set, subscription database is set, subscribing manner is set, priority is set, subscription status are set successively then, and the method Add of last allocating object MergePublication adds object MergeSubscription;
13) the turn-off data storehouse connects: the method Close of allocating object SQLServer finishes;
14) discharge the DMO environment: call method COMUninitialize finishes.
Should be understood that, for those of ordinary skills, can make various possible changes or replacement according to the explanation and the embodiment of technical scheme of the present invention, all these changes or replacement all belong to the protection domain of claim of the present invention.
Claims (9)
1, a kind of synchronization replication collocation method based on MS SQL Server, it is characterized in that: call the SQL-DMO api interface that MS SQLServer Database Systems provide, the operation steps that the database synchronization replication is disposed encapsulates, and described synchronization replication collocation method comprises four management objects at least: selection also connects publisher server management object, establishment release management object, selection Subscriber management object, establishment subscription management object; Described synchronization replication collocation method may further comprise the steps:
A) selection and connection publisher server;
B) create issue;
C) selection and connection Subscriber;
D) create subscription.
2, method according to claim 1 is characterized in that: described step a) provides external user interface, by user's input, selects the publisher server title.
3, method according to claim 1 is characterized in that: described step c) provides external user interface, by user's input, selects the Subscriber title.
4, method according to claim 1 is characterized in that: described step a) may further comprise the steps:
A1) execution environment of initialization DMO;
A2) the database server information of inquiry and registration to the local computer;
A3) select publisher server, account number and password;
A4) judge whether selecteed server is registered in group of server, if it is registered, then directly carry out the database bind command, verify whether successful connection, if selecteed server is not registered, then at first register operation, after succeeding in registration in group of server, carry out the database bind command again, and publisher server information is saved in the global variable.
5, method according to claim 1 is characterized in that: described step b) may further comprise the steps:
B1) at first from global variable, obtain the publisher server title, Distributor is set then;
B2) position of specifying snapshot document to press from both sides;
B3) enable publisher server, from global variable, obtain the publisher server title;
B4) select publication database;
B5) select the issue type, select the merge replication type;
B6) given subscription type of server;
B7) select the issue project;
B8) select issue to describe;
B9) self-defined issue attribute;
B10) start snapshot agent, initialization issue behind the startup snapshot agent.
6, method according to claim 3 is characterized in that: a following group selection value is arranged the sequence of steps b1 that described step b) comprises)～b10):
B11) at step b1) in, it is the default selection of system database that Distributor is set, promptly Distributor and publisher server are same server;
B21) at step b2) in, specifying the position of snapshot document folder is the default selection of database;
B41) at step b4) in, database to be released predefined is good;
B51) at step b5) in, predefined is good for the issue type;
B61) at step b6) in, the given subscription type of server is a MS SQL Server database server;
B81) at step b8) in, select default value not describe for having;
B91) at step b9) in, select database table is carried out by row, filters or do not filter by row.
7, method according to claim 1 is characterized in that: described step c) may further comprise the steps:
C1) select Subscriber, account number and password;
C2) judge whether selecteed server is registered in group of server, if it is registered, then directly carry out the database bind command, verify whether successful connection, if selecteed server is not registered in group of server, then at first register operation, after succeeding in registration, carry out the database bind command again and Subscriber information is saved in the global variable.
8, method according to claim 1 is characterized in that: described step d) may further comprise the steps:
D1) Subscriber is set;
D2) select destination data storehouse, i.e. subscription database;
D3) scheduling of merging Agent is set; Merging Agent uses with merge replication; Merge Agent and on Subscriber, use initial snapshot, and move and regulate the incremental data change that takes place after the establishment initial snapshot; Each merge to be subscribed to all own merging Agent, and this merges to act on behalf of and connects publisher server and Subscriber simultaneously and they are upgraded;
D4) after finishing the initialization issue, initialization is subscribed to;
D5) subscription priority being set is the database default value;
D6) start the Agent service, revise the scheduling that operation is acted on behalf of in merging.
9, method according to claim 1, it is characterized in that: described selection and connection publisher server management object are the CConnPublisher class, described establishment release management object is the CCreatePublication class, described selection Subscriber management object is the CConnSubscriber class, and described establishment subscription management object is the CCreateSubscription class.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNB2004100370359A CN100382030C (en) | 2003-12-12 | 2004-04-23 | Synchronous configuration copying method based on MS SQL Server |
Applications Claiming Priority (3)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN200310123615 | 2003-12-12 | ||
| CN200310123615.5 | 2003-12-12 | ||
| CNB2004100370359A CN100382030C (en) | 2003-12-12 | 2004-04-23 | Synchronous configuration copying method based on MS SQL Server |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN1547118A true CN1547118A (en) | 2004-11-17 |
| CN100382030C CN100382030C (en) | 2008-04-16 |
Family
ID=34378851
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CNB2004100370359A Expired - Fee Related CN100382030C (en) | 2003-12-12 | 2004-04-23 | Synchronous configuration copying method based on MS SQL Server |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN100382030C (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2007115477A1 (en) * | 2006-04-10 | 2007-10-18 | Huawei Technologies Co., Ltd. | Data synchronization method und system |
| CN106302473A (en) * | 2016-08-18 | 2017-01-04 | 深圳市金证科技股份有限公司 | The duplication maintaining method of a kind of SQL Server data base and system |
-
2004
- 2004-04-23 CN CNB2004100370359A patent/CN100382030C/en not_active Expired - Fee Related
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2007115477A1 (en) * | 2006-04-10 | 2007-10-18 | Huawei Technologies Co., Ltd. | Data synchronization method und system |
| US7899935B2 (en) | 2006-04-10 | 2011-03-01 | Huawei Technologies Co., Ltd. | Method and system for data synchronization |
| CN106302473A (en) * | 2016-08-18 | 2017-01-04 | 深圳市金证科技股份有限公司 | The duplication maintaining method of a kind of SQL Server data base and system |
| CN106302473B (en) * | 2016-08-18 | 2019-09-17 | 深圳市金证科技股份有限公司 | A kind of the duplication maintaining method and system of SQL Server database |
Also Published As
| Publication number | Publication date |
|---|---|
| CN100382030C (en) | 2008-04-16 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN1112642C (en) | Design part reusing method in configuration tool | |
| CN101047549A (en) | Data synchronous system and its method | |
| CN1291313C (en) | System and method for the automatic installation and configuration of an operating system | |
| CN1203425C (en) | Device and method of controlling intergroup resource utilization | |
| CN1298503A (en) | Dynamic lookup service in a distributed system | |
| CN1858704A (en) | Method of upgrading sequence | |
| CN1207847A (en) | System platform for communication system | |
| CN101079755A (en) | Configuration method of network element management system | |
| CN100341281C (en) | Method for realizing task management for network system | |
| CN1866221A (en) | Software interface testing method and apparatus | |
| CN1177152A (en) | Method for coordinating reproduction of series files of one access file | |
| CN1504880A (en) | Operating system automatically installing method applying Linux | |
| CN1946226A (en) | Method, device for upgrading telecommunication equipment and upgrading engine unit | |
| CN1277210C (en) | Method of document synchronization | |
| CN1869939A (en) | Method for access data base by multi-line program applied program | |
| CN1848111A (en) | Realizing method of a data operating interface used in internal-memory database | |
| CN1842078A (en) | Gridding service container | |
| CN1677932A (en) | Network management configuration method and apparatus thereof | |
| CN100337204C (en) | Online software updating method | |
| CN1547118A (en) | Synchronous configuration copying method based on MS SQL Server | |
| CN1091842A (en) | The interrupt system and the method that comprise user interface | |
| CN1924801A (en) | Solid mass-based software framework system and running method thereof | |
| CN1791027A (en) | Gridding information model system and method for modeling processing gridding information | |
| CN101030893A (en) | Method for controlling realtime monitor service | |
| CN101039219A (en) | Multifunctional network application equipment and starting and online updating method |
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 | ||
| ASS | Succession or assignment of patent right |
Owner name: JINJIANG HIGH-TECH DEVELOPMENT OFFICE Free format text: FORMER OWNER: ZTE CORPORATION Effective date: 20131107 |
|
| C41 | Transfer of patent application or patent right or utility model | ||
| COR | Change of bibliographic data |
Free format text: CORRECT: ADDRESS; FROM: 518057 SHENZHEN, GUANGDONG PROVINCE TO: 362200 QUANZHOU, FUJIAN PROVINCE |
|
| TR01 | Transfer of patent right |
Effective date of registration: 20131107 Address after: Jinjiang City, Fujian province 362200 Chongde road Quanzhou City No. 283 friends Jade Technology Building Patentee after: Jinjiang high and new technology development office Address before: 518057 Nanshan District, Guangdong high tech Industrial Park, science and Technology Industrial Park, ZTE building, block A, layer 6, layer Patentee before: ZTE Corporation |
|
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20080416 Termination date: 20170423 |
|
| CF01 | Termination of patent right due to non-payment of annual fee |