CN1791873B - Undrop objects and dependent objects in a database system - Google Patents
Undrop objects and dependent objects in a database system Download PDFInfo
- Publication number
- CN1791873B CN1791873B CN200480013535.7A CN200480013535A CN1791873B CN 1791873 B CN1791873 B CN 1791873B CN 200480013535 A CN200480013535 A CN 200480013535A CN 1791873 B CN1791873 B CN 1791873B
- Authority
- CN
- China
- Prior art keywords
- subordinate
- equipment
- subordinated
- described object
- eliminated
- 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.)
- Expired - Lifetime
Links
- 230000001419 dependent effect Effects 0.000 title abstract 4
- 238000000034 method Methods 0.000 claims abstract description 29
- 230000009467 reduction Effects 0.000 claims description 11
- 230000008859 change Effects 0.000 claims description 4
- 238000005192 partition Methods 0.000 abstract description 4
- 238000010926 purge Methods 0.000 abstract 1
- 230000008569 process Effects 0.000 description 12
- 238000010586 diagram Methods 0.000 description 10
- 238000004590 computer program Methods 0.000 description 5
- 238000005516 engineering process Methods 0.000 description 4
- 230000007246 mechanism Effects 0.000 description 3
- 230000005055 memory storage Effects 0.000 description 3
- 238000012545 processing Methods 0.000 description 2
- 238000011084 recovery Methods 0.000 description 2
- 238000004140 cleaning Methods 0.000 description 1
- 238000012217 deletion Methods 0.000 description 1
- 230000037430 deletion Effects 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 238000013507 mapping Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000008520 organization Effects 0.000 description 1
- 230000002085 persistent effect Effects 0.000 description 1
- 230000008707 rearrangement Effects 0.000 description 1
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/23—Updating
- G06F16/2379—Updates performed during online database operations; commit processing
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F2216/00—Indexing scheme relating to additional aspects of information retrieval not explicitly covered by G06F16/00 and subgroups
- G06F2216/09—Obsolescence
Landscapes
- Engineering & Computer Science (AREA)
- Databases & Information Systems (AREA)
- Theoretical Computer Science (AREA)
- Data Mining & Analysis (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
Techniques for undropping objects (e.g., tables) and dependent objects in a database systems are provided. When an object is dropped, the object is moved to a recycle bin where it resides until the user undrops the objects or the object is purged. Dependent objects are also moved into the recycle bin with the object to which they depend. The object can be purged from the recycle bin explicitly by a user or when more storage space is needed. Purging of dependent objects and partitions can be deferred if not required to obtain more storage space.
Description
Technical field
Relate generally to computer system of the present invention.More particularly, the present invention relates to provide object in the system of restoring data storehouse and the ability of subordinate object
Background technology
Conventionally, data base management system (DBMS) (DBMS) is the computer software of information integrity, tissue, storage, retrieval and security in controlling database.Information in database can be stored with polytype object.For example, information can be stored in table, and can make the access of the convenient his-and-hers watches of index of reference.Other common object comprises nested table, part table (partial table), index organization's table (IOT), large object (LOB), constraint, triggering etc.
For various reasons, user may determine to remove or delete object.For example, user may feel no longer to need object, will obtain more free memory or for contingency.No matter the reason of removing how, user changes sometimes his idea and wants to regain object.
For current database application, the current state of database is periodically stored.In addition, also stored the transaction list of from this state, database being carried out.When user wants to retrieve the object being eliminated, database will roll back to the state of last storage.After rollback, can carry out the affairs of carrying out after state is stored according to transaction list.
Although this scheme can be retrieved the object being eliminated, it has shortcoming relatively consuming time.What is more important, it also has following shortcoming: the rollback of database and before roll during, database generally can not be got rid of new affairs.Like this, during the object being eliminated in retrieval, in fact database is turned off.
Innovative technology for improvement of the object reset mode in Database Systems is useful.In addition it is useful, allowing searching object and need not require the innovative technology of database shutoff.
Summary of the invention
The invention provides for the object in restoring data storehouse and the innovative technology of subordinate object.Conventionally, when user wants to abandon or removes object, object is moved out of or is placed in recycle bin.The object that is subordinated to this object also can be transferred to recycle bin.Subsequently, if user wants to retrieve this object, this object can be moved out of recycle bin.Like this, the retrieval of object can be very fast, and do not need database to be turned off during retrieving.Specific embodiments more of the present invention have below been described.
In one embodiment, the invention provides a kind of method of carrying out restoring operation in relational database system, comprising: receive the order that abandons the object in relational database; Described object is moved on to recycle bin, and wherein said recycle bin is the table with following pattern, and described pattern has unique identification by the field of the described object being dropped; If there is the subordinate object that is subordinated to described object, described subordinate object moved on to described recycle bin; After receiving the order of the described object of reduction, during retrieving, do not require the in the situation that described database being turn-offed by reality described object and described subordinate object are shifted out to described recycle bin.
In another embodiment, the invention provides a kind of method of carrying out restoring operation in Database Systems, comprising: receive the order that abandons the object in relational database; Described object is moved on to recycle bin, and wherein said recycle bin is the table with following pattern, and described pattern has unique identification by the field of the described object being dropped; If there is the subordinate object that is subordinated to described object, described subordinate object moved on to described recycle bin; After receiving the order of the described object of reduction, during retrieving, do not require the in the situation that described database being turn-offed by reality described object is shifted out to described recycle bin; And if need storage space, remove described object in described recycle bin so that more storage space to be provided.
After explanation below having read and relevant accompanying drawing, other features and advantages of the present invention will become apparent, and in accompanying drawing, same or analogous structure is indicated with identical label.
accompanying drawing explanation
Fig. 1 shows the three-layer architecture example for data base management system (DBMS);
Fig. 2 illustrates the block diagram of the computer system of using in conjunction with the embodiment of the present invention;
Fig. 3 shows the block diagram of some example object in database;
Fig. 4 shows the process flow diagram flow chart of the object (if there is subordinate object, also comprising subordinate object) in restoring data storehouse;
Fig. 5 shows and can remove from recycle bin the process flow diagram flow chart of the various ways of object;
Fig. 6 shows from recycle bin and removes object to obtain the process flow diagram flow chart of more storage spaces;
Fig. 7 shows the table schema example of the recycle bin that can be used in fulfillment database system;
Fig. 8 shows for example, entry example in Fig. 7 table of object for being discarded in recycle bin (, table) and subordinate object.
Embodiment
In the following description, the embodiment with reference to the object in restoring data lab environment and subordinate object describes the present invention.Yet embodiments of the invention are not limited to any concrete architecture, environment, application or implementation.For example, although will describe the exemplary three-layer architecture for data base management system (DBMS), the present invention also can be conveniently used in database application or architecture.Therefore to the explanation of embodiment, be below, in illustrational object and unrestriced object.
Very conventional DBMS architecture is three-layer architecture as shown in Figure 1.Core in data base management system (DBMS) is the central storage means 1 of stored data base 3.Database 3 is generally stored on one or more hard disks, and database 3 is generally compared with a part for computation machine system.Information can utilize Relational DBMS to be stored in database 3 with multiple format, and wherein Relational DBMS extremely depends on and shows storage information.
In addition, one or more application servers 7 can provide user interface to database server 5.For example, application server 7 can be the web application server on the Internet (or other network).Application server 7 can provide user friendly mechanism, to pass through database server 5 accessing databases 3.Web browser 9 can be used for access application server 7.
Fig. 2 shows the block component diagram in the computer system that realizes the embodiment of the present invention.Computer system 101 comprises processor 103, for carrying out from the computer program instruction of (comprising operating system).Although processor generally also has high-speed cache, processor 103 use storeies 105 are stored instruction or computer code and data.
Fixed-storage device 107 can be stored computer program and data, and to make it be generally persistent and compare more storage is provided with storer 105.At present, the common fixed storage for database is many (for example, array) hard disk.Removable memory storage 109 provides movability to the computer program being stored thereon and/or data.The example of removable memory storage is floppy disk, tape, CD/ROM, flash memory device etc.
Storer 105, fixed-storage device 107 and removable memory storage 109 provide the computer-readable recording medium example that can be used for storage and obtain data that computer program, the present invention use etc., and wherein computer program comprises and realizes computer code of the present invention.In addition the data-signal (for example,, in comprising the network of the Internet) of realizing with carrier wave, can be computer-readable recording medium.Input 111 allows user and system to carry out alternately.Input can be by realizing with keyboard, mouse, button, dialing or any other input mechanism.The 113 permission systems of exporting provide output to user.Output can provide by monitor, display screen, LED, printer or any other output mechanism.
Network interface 115 permission systems connect with interface the network that it is connected to.The system bus architecture of computer system 101 is represented by arrow 117.Assembly shown in Fig. 2 can find in many computer systems.Yet assembly can be added, deletes and merge.For example, fixed-storage device 107 can be by the file server of network connected reference.Therefore, Fig. 2 is unrestriced object for illustrational object.
Now, exemplary database application and environment have been described, below example object in discussion database can be useful.Fig. 3 shows object and the subordinate object that may exist in database.
The table 201 illustrating comprises large object (LOB) 203.Table is for store the common object of information in database.Information is generally stored in the field of table, and can comprise the data type such as numeral, character string, pointer, nested table etc.General off-balancesheet except such as nested table, partition table, IOT etc., also has a variety of tables.
For illustrational object, the another type data that shown LOB 203 representatives can be stored in table.LOB can store the information such as binary picture and audio files.For access list 201 more effectively, show index 205 and 207.Index generally carrys out more effectively access list by key field.
LOB 203 and index 205 and 207 are examples of subordinate object, because they are subordinated to another object (table 201 in this example).They are subordinate objects, because if there is no the object of their institute's subordinates, subordinate object will almost or at all not be worth.
Some subordinate objects can be rebuild, and mean that, if subordinate object is eliminated, it can be rebuilt.Index 205 and 207 is examples of subordinate object that can be rebuilt.Once LOB 203 be eliminated generally can not be rebuilt subordinate object example.Other example of subordinate object comprises constraint and triggers, but the present invention can be advantageously used in working together with the subordinate object with any type.
Database is much complicated than shown in Fig. 3 generally.Yet this figure is being useful aspect the description embodiment of the present invention.
Fig. 4 shows reduction from the process flow diagram flow chart of the object of database.With shown all process flow diagrams are the same here, do not deviating under the condition of spirit and scope of the invention, can add, deletion, combination or rearrangement step.
In step 301, receive order and abandon object.Order generally receives from user, and can be by inputting such as the interface of graphic user interface or order line.By abandoning object, user represents that she thinks no longer needs this object (for example, table).
In step 303, object is moved to recycle bin.Recycle bin is such warehouse, and it is for storing the object being dropped, until user reduces them, user clearly removes them or database is removed them to obtain more storage space.Can be used for defining recycle bin by change has and so on variable carry out the movement to object.
In certain embodiments, recycle bin is implemented as dictionary table.When object is dropped, in this table, producing an entry and these objects can be reduced.Suitable user still can be distributed in the space of the object in recycle bin, even if they are dropped.Other details of an embodiment is described hereinafter with reference to Fig. 7 and Fig. 8.
In step 305, determine whether to exist any subordinate object that is subordinated to the object being dropped.If there is subordinate object, at step 307 subordinate object, be moved to recycle bin.For example, with reference to figure 3, if user's indicating gauge 201 should be dropped, system is by LOB 203 and index 205 and 207 being identified as to the subordinate object of table 201, so they will be moved to recycle bin.
With reference to figure 4, after receiving the order of reduction object, in step 309, this object is moved out of recycle bin.By object is shifted out to recycle bin, Database Systems can reduction tables and are not required that database is turn-offed by reality during retrieving.
When object is reduced and be moved out of recycle bin, all subordinate objects that exist in recycle bin also can be moved out of recycle bin (that is, reduction).In some instances, in order to obtain more storage spaces, can rebuild subordinate object may be eliminated from recycle bin.In Database Systems in processing requirements intermittently or any At All Other Times time, when needs can reconstructed object, rebuilt in the time of can rebuilding subordinate object and can be reduced at the object of its subordinate.
Fig. 4 shows the example how object and subordinate object can be moved on to recycle bin.Fig. 5 shows and can shift out from recycle bin the mode of object.More particularly, Fig. 5 shows and can remove from recycle bin the process flow diagram flow chart of object and subordinate object.
If in step 351, database is not in needing the state of more storage spaces, and user can fill order remove object and subordinate object from recycle bin.For example, in step 353, user can clearly remove object or subordinate object from recycle bin 353.Once object or subordinate object are eliminated, if user changes her idea, may need to carry out rollback and before roll so that searching object or subordinate object.
In addition,, in step 355, user can reduce object or subordinate object.By reduction object or subordinate object, object or subordinate object are moved out of recycle bin and available, as they are never dropped.
If need storage space, in step 357, database is by the object of selecting to remove.In step 359, database can be removed the subordinate object that is subordinated to selected objects in step 357.In step 361, selected objects is eliminated.
As mentioned above, in certain embodiments, if need more storage spaces, database is selected object and the subordinate object (if any) that will remove.In other embodiments, user can get involved this process, for example, select (one or more) object that will remove.
Because the object in recycle bin still takies storage space, so when object (or database need to create object) that user please look for novelty, will determine and need more storage space.Fig. 6 shows the process flow diagram flow chart that obtains more storage spaces by the one or more objects in removing recycle bin.
In step 401, receive the request to amount of memory.In step 403, select object at most to remove.Although in certain embodiments, selected object at most, other embodiment can select the object that will be eliminated by any characteristic.
In step 405, determine whether selected object is partitioned.If selected objects is not partitioned, at step 407 object, be eliminated.Being subordinated to the object that is eliminated object also can be eliminated.Yet, if because step 407 place provides the storage space of asking thereby do not needed to remove at this moment subordinate object the removing of object, the removing of subordinate object can be postponed till more late time.For example, in certain embodiments, demons (daemon) are at running background, and have been marked as the subordinate object that can remove but also not be eliminated in identification recycle bin.Demons can at the convenient time be removed these subordinate objects subsequently.
In step 409, determining whether also needs more storage space, if "Yes", flow process is got back to step 403.Otherwise, obtained asked storage space.
Get back to now step 405, if object is partitioned, in step 411, remove one or more subregions.In certain embodiments, all subregions are eliminated.But, if all need to be eliminated in order to obtain the not every subregion of asked storage space, only have those subregions to be removed at once.As mentioned above, other subregion can be marked as and can remove, and demons can be removed these programs from recycle bin in more late.Like this, a part for object (for example, one or more subregions) can be marked as in the future and remove.
By required object or the subregion of storage space that only removing acquisition is asked, can find out, user's (or database) only needs to wait for the required time of storage space that obtains.Like this, user does not need removing subordinate object by her unwanted storage space or this process of subregion is waited for.For this reason, in certain embodiments, when user clearly removes object, this object, all subordinate objects and all subregions are removed (that is, not having demons to postpone to remove) at once, so because be the delay that order that user sends can cause processing.
example
As mentioned above, recycle bin may be implemented as table.This table can comprise the entry of each object being dropped.Fig. 7 shows for realizing the table schema example of recycle bin, and below by the concrete field of instruction card.
OBJ# storage is dropped the primary object number of object.This field is used to represent the object in dictionary table.OBJ# is unique for all objects in database, has therefore formed the unique identifier for object.
For the situation of subregion, when being moved to recycle bin, it will create a new object, and therefore a new OBJ# can be assigned to it.This new OBJ# can be used for identifying relevant partitions subsequently.In certain embodiments, if subregion is reduced, it will be resumed as new object.
OWNER# is used to the original owner's of storage object USER#.When abandoning object, owner's information of this object may be modified.If user reduces object, it should be restored to original owner, and this can utilize this field to realize.
ORIGINAL_NAME# keeps the original title of object.The title of object may change when it is moved to recycle bin.The original title of service object is the convenience for user.
The DDL operation that OPERATION regulation is carried out object.This field can be used for distinguishing to as if be dropped or by brachymemma, thereby can suitably process object.This field can keep one of following two effective values: 0-object is dropped (DROP) and 1-object by brachymemma (TRUNCATE).
TYPE# storage is dropped the object type of object.The examples of types that can be supported for reducing below: table, conventional index, bitmap index, nested table, LOB, LOB index, Domain Index, IOT acrochordal draw, the IOT section of overflowing, IOT mapping table, triggering, constraint, table subregion, the synthetic subregion of table, index partition, the synthetic subregion of index, LOB subregion, the synthetic subregion of LOB etc.
TS# provides the table space number that is dropped and is moved to now the object of recycle bin.This can be useful for attempting for the table space Free up Memory close to filling up.From still having the table space recovery space of large quantity space, can not solve space pressure problem, be only therefore useful for almost filling up and needing the table space in some spaces from recycle bin recovery space.
The document number of the paragraph header of FILE# storage object.Together with BLOCK#, can obtain unique SEG $ entry with TS#.
BLOCK# provides the piece number of the paragraph header of object.Together with FILE#, can obtain unique SEG $ entry with TS#.This field can be used for effectively accessing paragraph header when having living space pressure.
The system time of DROPTIME storage when object is dropped.The value of this field can be used for calculating object time in recycle bin Already in.In the situation that having living space pressure, the order that can be dropped with object is from recycle bin recycle object.Like this, this field is used to maintain the time-based sequence of the object in recycle bin.
DROPSCN provides the SCN that causes that object abandons.This can be useful for flash back (Flash Back) inquiry.
The title of the subregion that PARTITIOM_NAME maintenance is dropped.In case of non-partitioned tables, this field is NULL.Therefore, use this field to be only used to user's convenience.
FLAGS keeps a plurality of signs of the object in recycle bin.Whether one of a plurality of positions of this field can be used for keeping tracing object can be reduced.If increment method is used to space reclamation, probably only there is the few scope (extent) that belongs to object to be released and other scope is still present in recycle bin.If be released without any the scope that is assigned to this object, object can be reduced.Even be released if only belong to a scope of object, it should not be reduced yet.
The OBJ# of the parent object of the object that RELATED sign is considered.
BO storage causes that this object is dropped and is placed in the OBJ# of the base table in recycle bin.
PURGEOBJ provides the OBJ# of following object, wherein said object (for example, index or table) in the situation that wanting from this special object of System Cleaning Free up Memory because space pressure will be eliminated.
The table space number of BASE_TS# storage base object (for example, table).
BASE_OWNER# keeps the owner's of base object user number.
SPACE provides the size of object.This field can be used for showing the object in recycle bin has been used the how many spaces form of piece number (for example, with).
CON# is stored in the constraint ID under the situation of the index building due to constraint.Otherwise it will be NULL.
SPARE1, SPARE2 and SPARE3 can be used in realization in the future.
Now, the table schema in Fig. 7 has been described, it is useful that the object be dropped and be placed in recycle bin and the example of subordinate object are discussed below.
When user abandons object, object is placed in recycle bin.This object is marked as and is dropped (but not being eliminated) in OBJ $.User can remove this object according to the idea of oneself, or this object will be removed automatically due to space pressure.
Fig. 8 shows the object that has been dropped and the entry of subordinate object.Table TABLE1 and index INDEX1 (subordinate object) that these entry indications have abandoned.When TABLE1 is dropped, these entries are added in table.
As seen in Fig., RELATED field indication INDEX1 is relevant with TABLE1.Therefore, INDEX1 is placed in recycle bin because TABLE1 is dropped.
First user is not reducing under the condition of TABLE1, can not reduce INDEX1, if but not retrieving the space from relevant object, the TABLE1 that reduces also will reduce INDEX1.When object need to be resumed (being reduced), by use original owner information from recycle bin (for example, OWNER#), so that object is re-assigned to it.Only have when object is eliminated (by user or space reclamation process), it will be removed from recycle bin, thereby the affairs in request space can be reused this space.
Although the preferred embodiments of the present invention have been carried out to complete explanation above, can use multiple replacement form, modification and equivalents.Clearly, by above-described embodiment is modified, can apply the present invention equally.For example, although can realize recycle bin by table schema, the invention is not restricted to above-mentioned concrete example.Therefore, explanation above should be as limitation of the scope of the invention, and scope of the present invention is limited by boundary line and the scope of claim and all equivalents thereof.
Claims (24)
1. in relational database system, carry out a method for restoring operation, comprising:
Reception abandons the order of the object in relational database;
To object store table, add entry, wherein said entry comprises that unique identification is by the field of the described object being dropped;
Determine whether to exist the one or more subordinate objects that are subordinated to described object, if existed, to described object store table, add one or more additional entries, wherein each additional entries comprises the field of a subordinate object in one or more subordinate objects described in unique identification and the field of the described object that the described subordinate object of sign is subordinated to;
By change be used for defining described object store have and so on variable abandon in described relational database by the described object being dropped and described subordinate object; And
After receiving the order of the described object of reduction, utilize the entry in described object store table that described object and subordinate object thereof are returned to described relational database.
2. the method for claim 1, also comprises the described object of removing in described object store table.
3. the method for claim 1, also comprises that the described object of removing in described object store table to obtain more storage spaces in described relational database.
4. the method for claim 1, also comprises the request receiving amount of memory.
5. method as claimed in claim 4, also comprises that the object of removing in described object store table is to obtain described amount of memory.
6. method as claimed in claim 4, also comprises and removes the subordinate object that is subordinated to the object being eliminated.
7. method as claimed in claim 4, also comprises if need to obtain described amount of memory, removes the subordinate object that is subordinated to the object being eliminated, and all other subordinate objects are labeled as in the future and are removed.
8. method as claimed in claim 4, also comprises if a part for object does not need to be eliminated to obtain described amount of memory, described part is labeled as in the future and removes.
9. the method for claim 1, wherein after receiving the order of reduction object, the method also comprises judging whether described object is the subordinate object that is subordinated to a parent object, and if be, only in the situation that described parent object has been reduced, just reduces described object.
10. the method for claim 1, wherein said to liking table, and described subordinate object comprises at least one that select in the group from being comprised of large object and index.
11. methods as claimed in claim 8, wherein said object is partitioned, and the described part of described object at least one subregion that is described object.
12. the method for claim 1, also comprise:
Remove described subordinate object; And
After being eliminated, removes described subordinate object described object.
13. 1 kinds of equipment that carry out restoring operation in relational database system, comprising:
For receiving the device of the order of the object that abandons relational database;
For adding bar destination device to object store table, wherein said entry comprises that unique identification is by the field of the described object being dropped;
For determining whether to exist the one or more subordinate objects that are subordinated to described object, and if exist, to described object store table, add one or more additional strip destination devices, wherein each additional entries comprises the field of a subordinate object in one or more subordinate objects described in unique identification and the field of the described object that the described subordinate object of sign is subordinated to;
For by change, be used for defining described object store have and so on variable abandon described relational database by the described object being dropped and the device of described subordinate object; And
For after receiving the order of the described object of reduction, utilize the entry in described object store table described object and subordinate object thereof to be returned to the device of described relational database.
14. equipment as claimed in claim 13, also comprise for removing the device of the described object of described object store table.
15. equipment as claimed in claim 13, also comprise that described object for removing described object store table to obtain the device of more storage spaces in described relational database.
16. equipment as claimed in claim 13, also comprise for receiving the device to the request of amount of memory.
17. equipment as claimed in claim 16, also comprise that object for removing described object store table is to obtain the device of described amount of memory.
18. equipment as claimed in claim 16, also comprise for removing the device of the subordinate object that is subordinated to the object being eliminated.
19. equipment as claimed in claim 16, if also comprise the subordinate object that is subordinated to the object being eliminated for obtaining described amount of memory, remove, and are labeled as all other subordinate objects in the device of removing in the future.
20. equipment as claimed in claim 16, if also comprise that the part for object does not need to be eliminated to obtain described amount of memory, are labeled as described part the device of removing in the future.
21. equipment as claimed in claim 13, wherein after receiving the order of reduction object, this equipment also comprises for judging whether described object is the subordinate object that is subordinated to a parent object, and if be, only in the situation that being reduced, described parent object just reduces the device of described object.
22. equipment as claimed in claim 13, wherein said to liking table, and described subordinate object comprises at least one that select in the group from being comprised of large object and index.
23. equipment as claimed in claim 20, wherein said object is partitioned, and the described part of described object at least one subregion that is described object.
24. equipment as claimed in claim 13, also comprise:
For removing the device of described subordinate object; And
For remove the device of described object after described subordinate object is eliminated.
Applications Claiming Priority (3)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| US10/445,793 | 2003-05-27 | ||
| US10/445,793 US8521789B2 (en) | 2003-05-27 | 2003-05-27 | Undrop objects and dependent objects in a database system |
| PCT/US2004/010616 WO2004107215A1 (en) | 2003-05-27 | 2004-04-07 | Undrop objects and dependent objects in a database system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN1791873A CN1791873A (en) | 2006-06-21 |
| CN1791873B true CN1791873B (en) | 2014-01-15 |
Family
ID=33450939
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN200480013535.7A Expired - Lifetime CN1791873B (en) | 2003-05-27 | 2004-04-07 | Undrop objects and dependent objects in a database system |
Country Status (7)
| Country | Link |
|---|---|
| US (1) | US8521789B2 (en) |
| EP (1) | EP1627334B1 (en) |
| JP (1) | JP2007501476A (en) |
| CN (1) | CN1791873B (en) |
| AU (1) | AU2004244168B2 (en) |
| CA (1) | CA2522047A1 (en) |
| WO (1) | WO2004107215A1 (en) |
Families Citing this family (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6920460B1 (en) * | 2002-05-29 | 2005-07-19 | Oracle International Corporation | Systems and methods for managing partitioned indexes that are created and maintained by user-defined indexing schemes |
| US7634510B2 (en) * | 2004-10-05 | 2009-12-15 | Oracle International Corporation | Method and system for time-based reclamation of objects from a recycle bin in a database |
| US7636737B2 (en) * | 2005-12-20 | 2009-12-22 | Microsoft Corporation | Web site multi-stage recycling |
| CN101546311B (en) * | 2008-03-27 | 2012-05-02 | 北京铭万互联科技有限公司 | Data processing method and data processing device for recycle bin |
| US8380702B2 (en) * | 2009-03-10 | 2013-02-19 | Oracle International Corporation | Loading an index with minimal effect on availability of applications using the corresponding table |
| CN102750198B (en) * | 2011-04-20 | 2016-01-20 | 腾讯科技（深圳）有限公司 | A kind of backup method of social network sites content and system |
| WO2014042648A1 (en) * | 2012-09-14 | 2014-03-20 | Empire Technology Development Llc | Cloud-based trash-can |
| CN104246716B (en) * | 2012-12-19 | 2018-02-09 | 华为技术有限公司 | The processing method and equipment of memory space object |
| US9589008B2 (en) * | 2013-01-10 | 2017-03-07 | Pure Storage, Inc. | Deduplication of volume regions |
| US10503766B2 (en) | 2014-09-29 | 2019-12-10 | Hewlett Packard Enterprise Development Lp | Retain data above threshold |
| US20180018356A1 (en) * | 2016-07-13 | 2018-01-18 | Deepspace Storage Systems Inc. | Relational database online storage manager |
| CN112181938A (en) * | 2019-07-05 | 2021-01-05 | 杭州海康威视数字技术股份有限公司 | Database cleaning method, device and computer readable storage medium |
Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1201950A (en) * | 1998-05-08 | 1998-12-16 | 中国人民解放军济南医学高等专科学校 | Method for deleting and restoring lines of table in database |
Family Cites Families (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US83064A (en) * | 1868-10-13 | Improved gearing for grindstones | ||
| US6246410B1 (en) | 1996-01-19 | 2001-06-12 | International Business Machines Corp. | Method and system for database access |
| US5767851A (en) | 1996-01-29 | 1998-06-16 | Sun Microsystems, Inc. | Method and apparatus for emulating an environment's drag and drop functionality in a host environment |
| US5802514A (en) | 1996-04-09 | 1998-09-01 | Vision Software Tools, Inc. | Automated client/server development tool using drag-and-drop metaphor |
| JPH10240592A (en) * | 1996-12-27 | 1998-09-11 | Fujitsu Ltd | Device and method for showing dependency relation of file |
| CA2279028C (en) | 1999-07-29 | 2002-09-10 | Ibm Canada Limited-Ibm Canada Limitee | Dropped database table recovery |
| US6591295B1 (en) | 1999-11-05 | 2003-07-08 | Oracle International Corp. | Methods and apparatus for using multimedia data stored in a relational database in web applications |
| US6611836B2 (en) | 2000-12-26 | 2003-08-26 | Simdesk Technologies, Inc. | Server-side recycle bin system |
| JP2002278821A (en) * | 2001-03-22 | 2002-09-27 | Sharp Corp | System and method for managing data and program for providing computer with data managing system |
| JP2002366410A (en) * | 2001-06-06 | 2002-12-20 | Fujitsu Ltd | Trash box server and trash box processing program |
| JPWO2003001422A1 (en) * | 2001-06-26 | 2004-10-14 | 俊行 谷 | How to provide transaction information |
| JP4284896B2 (en) * | 2001-08-02 | 2009-06-24 | コニカミノルタビジネステクノロジーズ株式会社 | File management program, computer-readable recording medium storing file management program, and file management method |
-
2003
- 2003-05-27 US US10/445,793 patent/US8521789B2/en active Active
-
2004
- 2004-04-07 CN CN200480013535.7A patent/CN1791873B/en not_active Expired - Lifetime
- 2004-04-07 EP EP04785596A patent/EP1627334B1/en not_active Expired - Lifetime
- 2004-04-07 AU AU2004244168A patent/AU2004244168B2/en not_active Expired
- 2004-04-07 WO PCT/US2004/010616 patent/WO2004107215A1/en active Application Filing
- 2004-04-07 JP JP2006532383A patent/JP2007501476A/en active Pending
- 2004-04-07 CA CA002522047A patent/CA2522047A1/en not_active Abandoned
Patent Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1201950A (en) * | 1998-05-08 | 1998-12-16 | 中国人民解放军济南医学高等专科学校 | Method for deleting and restoring lines of table in database |
Also Published As
| Publication number | Publication date |
|---|---|
| AU2004244168A1 (en) | 2004-12-09 |
| US8521789B2 (en) | 2013-08-27 |
| JP2007501476A (en) | 2007-01-25 |
| US20040243624A1 (en) | 2004-12-02 |
| EP1627334B1 (en) | 2012-09-26 |
| AU2004244168B2 (en) | 2009-11-26 |
| CA2522047A1 (en) | 2004-12-09 |
| CN1791873A (en) | 2006-06-21 |
| EP1627334A1 (en) | 2006-02-22 |
| WO2004107215A1 (en) | 2004-12-09 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US5237681A (en) | Relational data base memory utilization analyzer | |
| US6243718B1 (en) | Building indexes on columns containing large objects | |
| US7418544B2 (en) | Method and system for log structured relational database objects | |
| US8706779B2 (en) | System and method for data storage | |
| CN105868228A (en) | In-memory database system providing lockless read and write operations for OLAP and OLTP transactions | |
| CA2302303A1 (en) | System for accessing database tables mapped into memory for high performance | |
| JP2005530242A (en) | Storage system having partitioned movable metadata | |
| CN1791873B (en) | Undrop objects and dependent objects in a database system | |
| WO1992021090A9 (en) | Relational data base memory utilization analyzer | |
| WO2001016799A1 (en) | Method and system for supporting multiple, historical and future designs in a relational database | |
| JP4199888B2 (en) | Database management method | |
| US20170024457A1 (en) | Columnwise Range K-Nearest Neighbors Search Queries | |
| US6792429B2 (en) | Method for fault tolerant modification of data representation in a large database | |
| Rotem et al. | Extendible arrays for statistical databases and OLAP applications | |
| US7475088B2 (en) | Systems and methods of providing data from a data source to a data sink | |
| US20030200220A1 (en) | Method, system, and program product for the implementation of an attributegroup to aggregate the predefined attributes for an information entity within a content management system | |
| US20130006921A1 (en) | Method For Transferring Data into Database Systems | |
| US8510269B2 (en) | Uninterrupted database index reorganization/movement | |
| CN111581123A (en) | Class-based locking of memory allocations | |
| US7779057B2 (en) | Method and apparatus for retrieving and sorting entries from a directory | |
| JP3980326B2 (en) | Data management method and computer-readable recording medium | |
| Yang | A class of hybrid list file organizations | |
| CN115827653A (en) | Pure column type updating method and device for HTAP and mass data | |
| CN117493388A (en) | Data management method based on key value storage system and related equipment thereof | |
| CN115905259A (en) | Pure column type updating method and device supporting row-level concurrent control |
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 | ||
| CX01 | Expiry of patent term | ||
| CX01 | Expiry of patent term |
Granted publication date: 20140115 |