US20090070304A1 - Low-overhead built-in timestamp column for relational database systems - Google Patents

Low-overhead built-in timestamp column for relational database systems Download PDF

Info

Publication number
US20090070304A1
US20090070304A1 US12/272,718 US27271808A US2009070304A1 US 20090070304 A1 US20090070304 A1 US 20090070304A1 US 27271808 A US27271808 A US 27271808A US 2009070304 A1 US2009070304 A1 US 2009070304A1
Authority
US
United States
Prior art keywords
timestamp
column
hidden
data
timestamp column
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.)
Abandoned
Application number
US12/272,718
Inventor
Yao-Ching Stephen Chen
Curt L. Cotner
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
International Business Machines Corp
Original Assignee
International Business Machines Corp
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by International Business Machines Corp filed Critical International Business Machines Corp
Priority to US12/272,718 priority Critical patent/US20090070304A1/en
Publication of US20090070304A1 publication Critical patent/US20090070304A1/en
Abandoned legal-status Critical Current

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/28Databases characterised by their database models, e.g. relational or object models
    • G06F16/284Relational databases
    • YGENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10TECHNICAL SUBJECTS COVERED BY FORMER USPC
    • Y10STECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10S707/00Data processing: database and file management or data structures
    • Y10S707/99931Database or file accessing
    • Y10S707/99933Query processing, i.e. searching
    • YGENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10TECHNICAL SUBJECTS COVERED BY FORMER USPC
    • Y10STECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10S707/00Data processing: database and file management or data structures
    • Y10S707/99941Database schema or data structure
    • Y10S707/99943Generating database or data structure, e.g. via user interface

Definitions

  • the present invention relates to database systems, and more particularly to providing timestamps in database systems.
  • timestamps are typically used to indicate which rows have been modified since the last update.
  • a timestamp column that is automatically updated each time a row is modified is provided for this purpose. If the timestamp value in the timestamp column is later than the time of the last update, then that row has been modified since the last update.
  • Timestamp column for controlling optimistic locking schemes as follows: the application retrieves one or more rows from the table, including the timestamp column; the application logically or physically disconnects from the database system; the application makes updates to the rows that were retrieved from the database; and sometime later, the application reconnects to the database so that it can record the updates in the database.
  • the application Before sending each update, the application retrieves the row from the database to validate that the timestamp column has not changed since the data was originally retrieved. If the timestamp column is unchanged, the application can safely record the update for that row. If the timestamp column is not the same, the disconnected update fails, and the application has to re-drive the update process using the modified data row.
  • the improved timestamp should require low overhead, be available for all tables in a database system, and avoid problems for applications that do not expect a timestamp column.
  • the present invention addresses such a need.
  • the automatically updated timestamp can be provided in a hidden timestamp column for a table, where the value of the timestamp column can be retrieved with a query that calls the column by name.
  • the timestamp column can be provided for each table in the database system to ensure its availability to applications.
  • an automatically updated timestamp can be provided for a data page. This timestamp can be retrieved from an update timestamp recorded on disk and in the buffer pool or from a log relative byte address. Although this is a page-level timestamp, its use may be desirable for infrequently updated tables or where space on the disk and buffer pool is at a premium.
  • FIG. 1 illustrates a first preferred embodiment of an automatically updated timestamp for database systems in accordance with the present invention.
  • FIG. 2 illustrates a second preferred embodiment of an automatically updated timestamp for database systems in accordance with the present invention.
  • the present invention provides an improved automatically updated timestamp for database systems.
  • the following description is presented to enable one of ordinary skill in the art to make and use the invention and is provided in the context of a patent application and its requirements.
  • Various modifications to the preferred embodiment will be readily apparent to those skilled in the art and the generic principles herein may be applied to other embodiments.
  • the present invention is not intended to be limited to the embodiment shown but is to be accorded the widest scope consistent with the principles and features described herein.
  • FIGS. 1 and 2 in conjunction with the discussion below.
  • FIG. 1 illustrates a first preferred embodiment of an automatically updated timestamp for database systems in accordance with the present invention.
  • a built-in hidden timestamp column 101 is provided for each table in the database system that contains an automatically updated timestamp.
  • the timestamp column 101 is automatically updated with the last time that its corresponding row was modified.
  • the timestamp column 101 is “hidden” in that it does not appear in the database schema by default.
  • Application programs can specifically request that the timestamp column 101 be returned by issuing a query which calls the timestamp column 101 by name. This allows the value of the timestamp column 101 to be returned when required but avoids exposing the column 101 to queries that do not call it by name.
  • the timestamp column 101 does not show up in queries by applications that have no need for this column. This also allows the database administrator to add the timestamp column 101 to an existing table without worrying that the new column 101 will cause problems for existing application programs that do not expect the column to be present.
  • the hidden timestamp column 101 can be made available for all tables in the database system as a default. This avoids situations where the customer neglects to add the extra timestamp column 101 to a given table. However, in some cases the customer may not want to expend the CPU time or the disk space/buffer pool space required to have an automatically updated timestamp column on every row in every table. In these cases, it can be left to the customer to explicitly add the hidden timestamp column.
  • FIG. 2 illustrates a second preferred embodiment of an automatically updated timestamp for database systems in accordance with the present invention.
  • the database system obtains an automatically updated timestamp from the data page 200 . This can be accomplished in one of two ways.
  • an update timestamp 201 is available in the data page 200 that is recorded on disk or in the buffer pool. This update timestamp 201 can be used to indicate the last time one of the rows in the data page was modified.
  • the database system will have a log relative byte address (RBA) 202 associated with the last update to the data page 200 .
  • RBA log relative byte address
  • the RBA value 202 can be converted to a timestamp by taking periodic timestamp values and associating those values with the matching log RBA value. Given those periodic values, the timestamp for any given RBA value can be calculated by interpolating between the nearest periodic log RBA timestamps.
  • Timestamp column 101 Customers that choose to not create a timestamp column for a given table will still have the functional ability to retrieve a timestamp to determine if a row in the data page 200 has been changed or not. Since the timestamp is associated with the data page 200 rather than a single row, this timestamp will provide less granularity than the timestamp column 101 in the first preferred embodiment. However, this lesser granularity may be acceptable for tables that are updated infrequently. Therefore, the customer is given the flexibility to chose between using the hidden timestamp column 101 or the page-level timestamp 201 / 202 . In addition, the customer may choose to use the hidden timestamp column for one table, while using the page-level timestamp for another table.
  • the automatically updated timestamp can be provided in a hidden timestamp column for a table, where the value of the timestamp column can be retrieved with a query that calls the column by name.
  • the timestamp column can be provided for each table in the database system to ensure its availability to applications.
  • an automatically updated timestamp can be provided for a data page. This timestamp can be retrieved from an update timestamp recorded on disk and in the buffer pool or from a log relative byte address. Although this is a page-level timestamp, its use may be desirable for infrequently updated tables or where space on the disk and buffer pool is at a premium.

Abstract

An improved automatically updated timestamp for database systems is disclosed. The automatically updated timestamp can be provided in a hidden timestamp column for a table, where the value of the timestamp column can be retrieved with a query that calls the column by name. Optionally, the timestamp column can be provided for each table in the database system to ensure its availability to applications. For cases where a timestamp for each row in a table is not desired, an automatically updated timestamp can be provided for a data page. This timestamp can be retrieved from an update timestamp recorded on disk and in the buffer pool or from a log relative byte address. Although this is a page-level timestamp, its use may be desirable for infrequently updated tables or where space on the disk and buffer pool is at a premium.

Description

    CROSS-REFERENCE TO RELATED APPLICATIONS
  • Under 35 USC § 120, this application is a continuation application and claims the benefit of priority to U.S. patent application Ser. No. 10/777,604, filed Feb. 11, 2004, entitled “LOW-OVERHEAD BUILT-IN TIMESTAMP COLUMN FOR RELATIONAL DATABASE SYSTEMS”, all of which is incorporated herein by reference.
  • FIELD OF THE INVENTION
  • The present invention relates to database systems, and more particularly to providing timestamps in database systems.
  • BACKGROUND OF THE INVENTION
  • The need for data replication in a database system, particularly a distributed database system, is well known in the art. To ensure data consistency, modifications to different copies of a table must be replicated across all copies. To facilitate the updating of the table copies, timestamps are typically used to indicate which rows have been modified since the last update. Conventionally, a timestamp column that is automatically updated each time a row is modified is provided for this purpose. If the timestamp value in the timestamp column is later than the time of the last update, then that row has been modified since the last update.
  • Applications commonly use this timestamp column for controlling optimistic locking schemes as follows: the application retrieves one or more rows from the table, including the timestamp column; the application logically or physically disconnects from the database system; the application makes updates to the rows that were retrieved from the database; and sometime later, the application reconnects to the database so that it can record the updates in the database.
  • Before sending each update, the application retrieves the row from the database to validate that the timestamp column has not changed since the data was originally retrieved. If the timestamp column is unchanged, the application can safely record the update for that row. If the timestamp column is not the same, the disconnected update fails, and the application has to re-drive the update process using the modified data row.
  • As disconnected update models become more pervasive, the value of having an automatically updated timestamp column is growing. However, the addition of a timestamp column has several drawbacks. First, it requires additional CPU cost to maintain the timestamp column in each data row. Second, some tables may not be updated very frequently, so it may not be worthwhile to require the additional space for the timestamp in every row. Third, if the timestamp column has to be explicitly added to the table by the user, shrink-wrapped client applications cannot assume that the timestamp column will necessarily be present, since the user may have chosen not to add the timestamp column. So, client applications will be reluctant to exploit this feature of the database. Fourth, having an explicit column for the timestamp is also inconvenient for cases where some applications need the extra column while others do not. For example, adding the extra timestamp column for one application might cause problems for other existing applications that didn't expect this extra column to be part of the table schema.
  • Accordingly, there exists a need for an improved automatically updated timestamp for database systems. The improved timestamp should require low overhead, be available for all tables in a database system, and avoid problems for applications that do not expect a timestamp column. The present invention addresses such a need.
  • SUMMARY OF THE INVENTION
  • An improved automatically updated timestamp for database systems is disclosed. The automatically updated timestamp can be provided in a hidden timestamp column for a table, where the value of the timestamp column can be retrieved with a query that calls the column by name. Optionally, the timestamp column can be provided for each table in the database system to ensure its availability to applications. For cases where a timestamp for each row in a table is not desired, an automatically updated timestamp can be provided for a data page. This timestamp can be retrieved from an update timestamp recorded on disk and in the buffer pool or from a log relative byte address. Although this is a page-level timestamp, its use may be desirable for infrequently updated tables or where space on the disk and buffer pool is at a premium.
  • BRIEF DESCRIPTION OF THE FIGURES
  • FIG. 1 illustrates a first preferred embodiment of an automatically updated timestamp for database systems in accordance with the present invention.
  • FIG. 2 illustrates a second preferred embodiment of an automatically updated timestamp for database systems in accordance with the present invention.
  • DETAILED DESCRIPTION
  • The present invention provides an improved automatically updated timestamp for database systems. The following description is presented to enable one of ordinary skill in the art to make and use the invention and is provided in the context of a patent application and its requirements. Various modifications to the preferred embodiment will be readily apparent to those skilled in the art and the generic principles herein may be applied to other embodiments. Thus, the present invention is not intended to be limited to the embodiment shown but is to be accorded the widest scope consistent with the principles and features described herein.
  • To more particularly describe the features of the present invention, please refer to FIGS. 1 and 2 in conjunction with the discussion below.
  • FIG. 1 illustrates a first preferred embodiment of an automatically updated timestamp for database systems in accordance with the present invention. In the first preferred embodiment, a built-in hidden timestamp column 101 is provided for each table in the database system that contains an automatically updated timestamp. The timestamp column 101 is automatically updated with the last time that its corresponding row was modified. The timestamp column 101 is “hidden” in that it does not appear in the database schema by default. Application programs can specifically request that the timestamp column 101 be returned by issuing a query which calls the timestamp column 101 by name. This allows the value of the timestamp column 101 to be returned when required but avoids exposing the column 101 to queries that do not call it by name. Thus, the timestamp column 101 does not show up in queries by applications that have no need for this column. This also allows the database administrator to add the timestamp column 101 to an existing table without worrying that the new column 101 will cause problems for existing application programs that do not expect the column to be present.
  • Optionally, in order to ensure that applications can depend upon the automatically updated timestamp being present, the hidden timestamp column 101 can be made available for all tables in the database system as a default. This avoids situations where the customer neglects to add the extra timestamp column 101 to a given table. However, in some cases the customer may not want to expend the CPU time or the disk space/buffer pool space required to have an automatically updated timestamp column on every row in every table. In these cases, it can be left to the customer to explicitly add the hidden timestamp column.
  • Alternatively, the database system can obtain the value of the timestamp in other ways. FIG. 2 illustrates a second preferred embodiment of an automatically updated timestamp for database systems in accordance with the present invention. In the second preferred embodiment, the database system obtains an automatically updated timestamp from the data page 200. This can be accomplished in one of two ways. In some cases, an update timestamp 201 is available in the data page 200 that is recorded on disk or in the buffer pool. This update timestamp 201 can be used to indicate the last time one of the rows in the data page was modified. In the remaining cases, the database system will have a log relative byte address (RBA) 202 associated with the last update to the data page 200. The RBA value 202 can be converted to a timestamp by taking periodic timestamp values and associating those values with the matching log RBA value. Given those periodic values, the timestamp for any given RBA value can be calculated by interpolating between the nearest periodic log RBA timestamps.
  • Customers that choose to not create a timestamp column for a given table will still have the functional ability to retrieve a timestamp to determine if a row in the data page 200 has been changed or not. Since the timestamp is associated with the data page 200 rather than a single row, this timestamp will provide less granularity than the timestamp column 101 in the first preferred embodiment. However, this lesser granularity may be acceptable for tables that are updated infrequently. Therefore, the customer is given the flexibility to chose between using the hidden timestamp column 101 or the page-level timestamp 201/202. In addition, the customer may choose to use the hidden timestamp column for one table, while using the page-level timestamp for another table.
  • An improved automatically updated timestamp for database systems has been disclosed. The automatically updated timestamp can be provided in a hidden timestamp column for a table, where the value of the timestamp column can be retrieved with a query that calls the column by name. Optionally, the timestamp column can be provided for each table in the database system to ensure its availability to applications. For cases where a timestamp for each row in a table is not desired, an automatically updated timestamp can be provided for a data page. This timestamp can be retrieved from an update timestamp recorded on disk and in the buffer pool or from a log relative byte address. Although this is a page-level timestamp, its use may be desirable for infrequently updated tables or where space on the disk and buffer pool is at a premium.
  • Although the present invention has been described in accordance with the embodiments shown, one of ordinary skill in the art will readily recognize that there could be variations to the embodiments and those variations would be within the spirit and scope of the present invention. Accordingly, many modifications may be made by one of ordinary skill in the art without departing from the spirit and scope of the appended claims.

Claims (4)

1. A computer readable medium with program instructions for providing an automatically updated timestamp for database systems, comprising instructions for:
providing a table in the database system, the table including a plurality of rows of data;
providing a hidden timestamp column in the table of the database system, the hidden timestamp column including a timestamp value for each row of data in the table, the timestamp value indicating a last time a corresponding row of data in the table was previously modified, wherein the hidden timestamp column does not appear in the database schema by default and exposes the timestamp value for a given row of data in the table only to a query that calls the timestamp column by name;
receiving a query from an application to obtain a timestamp value from the hidden timestamp column, the query calling the timestamp column by name; and
in response to the query, the hidden timestamp column returning the timestamp value to the application for use by the application,
wherein the application uses the returned timestamp value for controlling a locking scheme associated with recording data updates in the database system wherein the locking scheme retrieves the hidden timestamp column.
2. The medium of claim 1, wherein the timestamp value corresponding to a given row of data in the table is automatically updated each time data in the given row has been modified.
3. A system, comprising:
a database system comprising at least one table, the at least one table including a plurality of rows of data;
an application capable of querying the database system;
a hidden timestamp column in the at least one table in the database system, the hidden timestamp column including a timestamp value for each row of data in the table, the timestamp value indicating a last time a corresponding row of data in the table was previously modified, wherein the hidden timestamp column does not appear in the database schema by default and exposes the timestamp value for a given row of data in the table only to a query that calls the timestamp column by name; and
means for receiving a query from an application to obtain a timestamp value from the hidden timestamp column, the query calling the timestamp column by name;
wherein the application uses the timestamp value for controlling a locking scheme associated with recording data updates in the database system wherein the locking scheme retrieves the hidden timestamp column.
4. The system of claim 3, wherein the timestamp value corresponding to a given row of data in the table is automatically updated each time data in the given row has been modified.
US12/272,718 2004-02-11 2008-11-17 Low-overhead built-in timestamp column for relational database systems Abandoned US20090070304A1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US12/272,718 US20090070304A1 (en) 2004-02-11 2008-11-17 Low-overhead built-in timestamp column for relational database systems

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US10/777,604 US7624119B2 (en) 2004-02-11 2004-02-11 Low-overhead built-in timestamp column for relational database systems
US12/272,718 US20090070304A1 (en) 2004-02-11 2008-11-17 Low-overhead built-in timestamp column for relational database systems

Related Parent Applications (1)

Application Number Title Priority Date Filing Date
US10/777,604 Continuation US7624119B2 (en) 2004-02-11 2004-02-11 Low-overhead built-in timestamp column for relational database systems

Publications (1)

Publication Number Publication Date
US20090070304A1 true US20090070304A1 (en) 2009-03-12

Family

ID=34827522

Family Applications (2)

Application Number Title Priority Date Filing Date
US10/777,604 Expired - Fee Related US7624119B2 (en) 2004-02-11 2004-02-11 Low-overhead built-in timestamp column for relational database systems
US12/272,718 Abandoned US20090070304A1 (en) 2004-02-11 2008-11-17 Low-overhead built-in timestamp column for relational database systems

Family Applications Before (1)

Application Number Title Priority Date Filing Date
US10/777,604 Expired - Fee Related US7624119B2 (en) 2004-02-11 2004-02-11 Low-overhead built-in timestamp column for relational database systems

Country Status (1)

Country Link
US (2) US7624119B2 (en)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20120260340A1 (en) * 2011-02-15 2012-10-11 Webroot Inc. Methods and apparatus for dealing with malware
CN110928890A (en) * 2019-11-08 2020-03-27 广州华多网络科技有限公司 Data storage method and device, electronic equipment and computer readable medium
US10803170B2 (en) 2005-06-30 2020-10-13 Webroot Inc. Methods and apparatus for dealing with malware

Families Citing this family (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7953749B2 (en) * 2004-05-11 2011-05-31 Oracel International Corporation Providing the timing of the last committed change to a row in a database table
US7493327B1 (en) * 2004-09-23 2009-02-17 Microsoft Corporation Schema-facilitated device capability discovery
CN101430687B (en) 2007-11-09 2015-11-25 阿里巴巴集团控股有限公司 Based on statistical form application process and the system of OLTP environment
US8489566B2 (en) * 2008-04-08 2013-07-16 International Business Machines Corporation Optimistic locking in online and offline environments
US9774676B2 (en) 2012-05-21 2017-09-26 Google Inc. Storing and moving data in a distributed storage system
US9298576B2 (en) 2012-06-04 2016-03-29 Google Inc. Collecting processor usage statistics
US9659038B2 (en) 2012-06-04 2017-05-23 Google Inc. Efficient snapshot read of a database in a distributed storage system
US9230000B1 (en) 2012-06-04 2016-01-05 Google Inc. Pipelining Paxos state machines
US9747310B2 (en) 2012-06-04 2017-08-29 Google Inc. Systems and methods of increasing database access concurrency using granular timestamps
US9449006B2 (en) 2012-06-04 2016-09-20 Google Inc. Method and system for deleting obsolete files from a file system
AU2015316450B2 (en) * 2014-11-12 2016-11-03 Huawei Cloud Computing Technologies Co., Ltd. Method for updating data table of KeyValue database and apparatus for updating table data
CN113221049B (en) * 2021-04-27 2023-09-01 北京奇艺世纪科技有限公司 Page updating method and device, electronic equipment and storage medium

Citations (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5721915A (en) * 1994-12-30 1998-02-24 International Business Machines Corporation Interaction between application of a log and maintenance of a table that maps record identifiers during online reorganization of a database
US5778354A (en) * 1995-06-07 1998-07-07 Tandem Computers Incorporated Database management system with improved indexed accessing
US5778350A (en) * 1995-11-30 1998-07-07 Electronic Data Systems Corporation Data collection, processing, and reporting system
US5812840A (en) * 1994-03-24 1998-09-22 Speedware Ltee./Ltd. Database query system
US6094649A (en) * 1997-12-22 2000-07-25 Partnet, Inc. Keyword searches of structured databases
US20010016844A1 (en) * 1998-10-27 2001-08-23 Amando B. Isip Method for maintaining exception tables for a check utility
US20010051939A1 (en) * 2000-06-12 2001-12-13 Mitsuhiko Yoshimura Method and system for querying database, as well as a recording medium for storing a database querying program
US6363389B1 (en) * 1998-09-24 2002-03-26 International Business Machines Corporation Technique for creating a unique quasi-random row identifier
US20030105732A1 (en) * 2000-11-17 2003-06-05 Kagalwala Raxit A. Database schema for structure query language (SQL) server
US6874001B2 (en) * 2001-10-05 2005-03-29 International Business Machines Corporation Method of maintaining data consistency in a loose transaction model
US6957221B1 (en) * 2002-09-05 2005-10-18 Unisys Corporation Method for capturing a physically consistent mirrored snapshot of an online database from a remote database backup system
US6996583B2 (en) * 2002-07-01 2006-02-07 International Business Machines Corporation Real-time database update transaction with disconnected relational database clients
US6999977B1 (en) * 2002-05-09 2006-02-14 Oracle International Corp Method and apparatus for change data capture in a database system

Patent Citations (14)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5812840A (en) * 1994-03-24 1998-09-22 Speedware Ltee./Ltd. Database query system
US5721915A (en) * 1994-12-30 1998-02-24 International Business Machines Corporation Interaction between application of a log and maintenance of a table that maps record identifiers during online reorganization of a database
US5778354A (en) * 1995-06-07 1998-07-07 Tandem Computers Incorporated Database management system with improved indexed accessing
US5778350A (en) * 1995-11-30 1998-07-07 Electronic Data Systems Corporation Data collection, processing, and reporting system
US6094649A (en) * 1997-12-22 2000-07-25 Partnet, Inc. Keyword searches of structured databases
US6363389B1 (en) * 1998-09-24 2002-03-26 International Business Machines Corporation Technique for creating a unique quasi-random row identifier
US20010016844A1 (en) * 1998-10-27 2001-08-23 Amando B. Isip Method for maintaining exception tables for a check utility
US20010051939A1 (en) * 2000-06-12 2001-12-13 Mitsuhiko Yoshimura Method and system for querying database, as well as a recording medium for storing a database querying program
US6882994B2 (en) * 2000-06-12 2005-04-19 Hitachi, Ltd. Method and system for querying database, as well as a recording medium for storing a database querying program
US20030105732A1 (en) * 2000-11-17 2003-06-05 Kagalwala Raxit A. Database schema for structure query language (SQL) server
US6874001B2 (en) * 2001-10-05 2005-03-29 International Business Machines Corporation Method of maintaining data consistency in a loose transaction model
US6999977B1 (en) * 2002-05-09 2006-02-14 Oracle International Corp Method and apparatus for change data capture in a database system
US6996583B2 (en) * 2002-07-01 2006-02-07 International Business Machines Corporation Real-time database update transaction with disconnected relational database clients
US6957221B1 (en) * 2002-09-05 2005-10-18 Unisys Corporation Method for capturing a physically consistent mirrored snapshot of an online database from a remote database backup system

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10803170B2 (en) 2005-06-30 2020-10-13 Webroot Inc. Methods and apparatus for dealing with malware
US11379582B2 (en) 2005-06-30 2022-07-05 Webroot Inc. Methods and apparatus for malware threat research
US20120260340A1 (en) * 2011-02-15 2012-10-11 Webroot Inc. Methods and apparatus for dealing with malware
US9413721B2 (en) * 2011-02-15 2016-08-09 Webroot Inc. Methods and apparatus for dealing with malware
US10574630B2 (en) 2011-02-15 2020-02-25 Webroot Inc. Methods and apparatus for malware threat research
CN110928890A (en) * 2019-11-08 2020-03-27 广州华多网络科技有限公司 Data storage method and device, electronic equipment and computer readable medium

Also Published As

Publication number Publication date
US7624119B2 (en) 2009-11-24
US20050177590A1 (en) 2005-08-11

Similar Documents

Publication Publication Date Title
US20090070304A1 (en) Low-overhead built-in timestamp column for relational database systems
US11030185B2 (en) Schema-agnostic indexing of distributed databases
US5758125A (en) Method of sharing data in a heterogeneous computer system
US8965849B1 (en) Static sorted index replication
US7389313B1 (en) System and method for creating a snapshot copy of a database
US10169438B2 (en) Determining common table definitions in distributed databases
US7676481B2 (en) Serialization of file system item(s) and associated entity(ies)
US9652346B2 (en) Data consistency control method and software for a distributed replicated database system
US8027993B2 (en) Techniques for establishing and enforcing row level database security
US8195607B2 (en) Fail over resource manager access in a content management system
US20120023116A1 (en) System and method for conversion of jms message data into database transactions for application to multiple heterogeneous databases
US8103624B2 (en) Apparatus and method for automating the logging of table changes in a database
US8615494B1 (en) Segment-based method for efficient file restoration
US8239402B1 (en) Standard file system access to data that is initially stored and accessed via a proprietary interface
US20060224642A1 (en) Production server to data protection server mapping
JP2004295870A (en) Consistency unit replication in application-defined system
US20170094032A1 (en) Referencing change(s) in data utilizing a network resource locator
US20170109246A1 (en) Database-level automatic storage management
US20060136439A1 (en) Method and system for modifying schema definitions
US20150169623A1 (en) Distributed File System, File Access Method and Client Device
US20050091233A1 (en) Method and system for preserving an original table schema
JP2015036868A (en) Database management device, database control method and program
US9342524B1 (en) Method and apparatus for single instance indexing of backups
KR102544820B1 (en) Micro service architecture based service system and method for multi-tenant configuration thereof
AU2002351296B2 (en) System and method for processing a request using multiple database units

Legal Events

Date Code Title Description
STCB Information on status: application discontinuation

Free format text: EXPRESSLY ABANDONED -- DURING EXAMINATION