Managing a computerized database using a volatile database table attribute
First Claim
1. A non-transitory computer-readable media having stored thereon an executable computer program for managing a computerized database, executable computer program instructs at least one computer system to perform actions comprising:
- storing at least one respective volatility attribute for each of at least one database table of said computerized database, each volatility attribute expressing volatility of at least a portion of a respective database table of said computerized database, said volatility of at least a portion of a respective database table being a property of the respective database table that is a function of changes to data recorded in said at least a portion of the respective database table with respect to time;
selectively determining whether to maintain at least one metadata structure, each metadata structure of the at least one metadata structure containing respective metadata describing data in at least a first database table of said at least one database table, the determining whether to maintain at least one metadata structure being performed using at least one volatility attribute expressing volatility of at least a portion of the first database table, wherein maintaining the at least one metadata structure comprises updating the metadata in the at least one metadata structure responsive to changes to the data in the at least a first database table; and
responsive to determining to maintain a first metadata structure of the at least one metadata structure, maintaining the first metadata structure, wherein maintaining the first metadata structure comprises updating the metadata in the first metadata structure responsive to changes to the data in the at least a first database table.
1 Assignment
0 Petitions
Accused Products
Abstract
A respective volatility attribute associated with each of one or more tables of a computerized database is used in any of various aspects to (a) determine how table data is stored in a physical storage device; (b) regulate the use of a materialized query table using database table data; and/or (c) influence circumstances under which indexes are created or advised by database analytic software. Various optional additional uses of a volatility attribute to manage a database are disclosed. Preferably, database parameters are automatically monitored over time and database table volatility state is automatically determined and periodically adjusted.
-
Citations
12 Claims
-
1. A non-transitory computer-readable media having stored thereon an executable computer program for managing a computerized database, executable computer program instructs at least one computer system to perform actions comprising:
-
storing at least one respective volatility attribute for each of at least one database table of said computerized database, each volatility attribute expressing volatility of at least a portion of a respective database table of said computerized database, said volatility of at least a portion of a respective database table being a property of the respective database table that is a function of changes to data recorded in said at least a portion of the respective database table with respect to time; selectively determining whether to maintain at least one metadata structure, each metadata structure of the at least one metadata structure containing respective metadata describing data in at least a first database table of said at least one database table, the determining whether to maintain at least one metadata structure being performed using at least one volatility attribute expressing volatility of at least a portion of the first database table, wherein maintaining the at least one metadata structure comprises updating the metadata in the at least one metadata structure responsive to changes to the data in the at least a first database table; and responsive to determining to maintain a first metadata structure of the at least one metadata structure, maintaining the first metadata structure, wherein maintaining the first metadata structure comprises updating the metadata in the first metadata structure responsive to changes to the data in the at least a first database table. - View Dependent Claims (2, 3, 4, 5, 6)
-
-
7. A computer system supporting a database, comprising:
-
a memory; at least one processor executing instructions contained in said memory; a database manager embodied as instructions stored in non-transitory media of said computer system and executable on said at least one processor, said database manager managing said database and providing access to data in at least one database table of said database; wherein said database manager stores at least one respective volatility attribute for each said at least one database table, each volatility attribute expressing volatility of at least a portion of the respective database table, each said volatility of at least a portion of a respective database table being a property of the respective database table that is a function of changes to data recorded in the at least a portion of the respective database table with respect to time; wherein said database manager further selectively determines whether to maintain at least one metadata structure, each metadata structure of the at least one metadata structure containing respective metadata describing data in at least a first database table of said at least one database table, the determining whether to maintain at least one metadata structure being performed using at least one volatility attribute expressing volatility of at least a portion of the first database table, wherein maintaining the at least one metadata structure comprises updating the metadata in the at least one metadata structure responsive to changes to the data in the at least a first database table; and wherein, responsive to determining to maintain a first metadata structure of the at least one metadata structure, said database manager further maintains the first metadata structure by updating the metadata in the first metadata structure responsive to changes to the data in the at least a first database table. - View Dependent Claims (8, 9, 10, 11, 12)
-
Specification