Deferred maintenance of sparse join indexes

[0001] This application is related to the following application filed on the same date herewith: Query Processing Using Horizontal Partial Covering Join Index 12/186,173.

[0002] In an active data warehouse (ADW), data are fed into base tables in near real time. A workload on the ADW is usually a mix of both long running strategic queries and short tactic queries, which are run against the same set of tables. Join indexes, especially aggregate join indexes, can improve the performance of strategic queries significantly by precalculating the joins and aggregations. However, the frequent update to the base table and the existence of join indexes in such an environment may bring a big maintenance overhead.

[0003] There are two approaches to maintain join indexes in a database management system (DBMS). In direct maintenance, a join index table is updated in the same transaction that updates the base table. In deferred maintenance, the join index table is updated at a different time from the update to the base table. Each approach has its own pros and cons. Direct maintenance guarantees the data freshness in the join index but the overhead of maintaining the join index in real time may be a performance concern. Deferred maintenance overcomes the performance obstacle by delaying the join index update but queries may return inconsistent results due to the synchronization problem between the base table and join index.

[0010] In the following description, reference is made to the accompanying drawings that form a part hereof, and in which is shown by way of illustration specific embodiments which may be practiced. These embodiments are described in sufficient detail to enable those skilled in the art to practice the invention, and it is to be understood that other embodiments may be utilized and that structural, logical and electrical changes may be made without departing from the scope of the present invention. The following description of example embodiments is, therefore, not to be taken in a limited sense, and the scope of the present invention is defined by the appended claims.

[0011] The functions or methods described herein may be implemented in software or a combination of software and human implemented procedures in one embodiment. The software may consist of computer executable instructions stored on computer readable media such as memory or other type of storage devices. The term “computer readable media” is also used to represent any means by which the computer readable instructions may be received by the computer, such as by different forms of wired or wireless transmissions. Further, such functions correspond to modules, which are software, hardware, firmware or any combination thereof. Multiple functions may be performed in one or more modules as desired, and the embodiments described are merely examples. The software may be executed on a digital signal processor, ASIC, microprocessor, or other type of processor operating on a computer system, such as a personal computer, server or other computer system.

[0012] A method of maintaining a join index emulates the performance of the deferred maintenance approach in a database management system (DBMS) while still maintaining accuracy in terms of query results. The maintenance method provides users control of both when to maintain the join index and to what extent the users would like to bring the join index up-to-date. In one embodiment, an underlying method to provide deferred maintenance is designed in such a way that an incremental part of the join index is calculated and merge deleted and merged into the join index table efficiently.

[0013] It is possible that the join index maintained in this way may not contain all the rows required in a query. By using a horizontal partial covering method, a query optimizer may still use the join index, and also be able to fetch the missing rows from the base table to give the complete answer to the query. The combination of these two methods may achieve good performance both in data loading and query processing. The join index may be maintained with a low cost in a short batch window.

[0014] A typical hardware and software environment is first described, followed by description of a horizontal partial covering method for fetching missing rows. Join index maintenance is then described.

[0015] Environment

[0016] FIG. 1 illustrates an example hardware and software environment that may be used to implement the join index maintenance and partial covering methods. A computer system 100 may be comprised of one or more processing units (PUs) 102, also known as processors or nodes, which may be interconnected by a network 104. Each of the PUs 102 may be coupled to zero or more fixed and/or removable data storage units (DSUs) 106, such as disk drives, that store one or more relational databases. Further, each of the PUs 102 may be coupled to zero or more data communications units (DCUs) 108, such as network interfaces, that communicate with one or more remote systems or devices.

[0017] Operators of the computer system 100 typically use a workstation 110, terminal, computer, handheld wireless device or other input device to interact with the computer system 100. This interaction generally comprises queries that conform to a Structured Query Language (SQL) standard, and invoke functions performed by a Relational Database Management System (RDBMS) executed by the system 100. In further embodiments, the computer system 100 may implement on-line analysis processing (OLAP) or multidimensional OLAP (MOLAP) or relational OLAP (ROLAP). Various other processing systems may also be implemented by computer system 100 or other computer systems capable of providing access to relational databases.

[0018] In one embodiment, the RDBMS comprises the Teradata® product offered by NCR Corporation, and may include one or more Parallel Database Extensions (PDEs) 112, Parsing Engines (PEs) 114, and Access Module Processors (AMPs) 116. These components of the RDBMS perform the function which enable of RDBMS and SQL standards, i.e., definition, compilation, interpretation, optimization, database access control, database retrieval, and database update.

[0019] Work may be divided among the PUs 102 in the system 100 by spreading the storage of a partitioned relational database 118 managed by the RDBMS across multiple AMPs 116 and the DSUs 106 (which are managed by the AMPs 116). Thus, a DSU 106 may store only a subset of rows that comprise a table in the partitioned database 118 and work is managed by the system 100 so that the task of operating on each subset of rows is performed by the AMP 116 managing the DSUs 106 that store the subset of rows.

[0020] The PEs 114 handle communications, session control, optimization and query plan generation and control. The PEs 114 fully parallelize all functions among the AMPs 116. As a result, the system of FIG. 1 applies a multiple instruction stream, multiple data stream (MIMD) concurrent processing architecture to implement a relational database management system 100.

[0021] Both the PEs 114 and AMPs 116 are known as “virtual processors” or “vprocs”. The vproc concept is accomplished by executing multiple threads or processes in a PU 102, wherein each thread or process is encapsulated within a vproc. The vproc concept adds a level of abstraction between the multi-threading of a work unit and the physical layout of the parallel processing computer system 100. Moreover, when a PU 102 itself is comprised of a plurality of processors or nodes, the vproc concept provides for intra-node as well as the inter-node parallelism.

[0022] The vproc concept results in better system 100 availability without undue programming overhead. The vprocs also provide a degree of location transparency, in that vprocs communicate with each other using addresses that are vproc-specific, rather than node-specific. Further, vprocs facilitate redundancy by providing a level of isolation/abstraction between the physical node 102 and the thread or process. The result is increased system 100 utilization and fault tolerance.

[0023] In various embodiments, data partitioning and repartitioning may be performed, in order to enhance parallel processing across multiple AMPs 116. For example, the data may be hash partitioned, range partitioned, or not partitioned at all (i.e., locally processed). Hash partitioning is a partitioning scheme in which a predefined hash function and map is used to assign records to AMPs 116, wherein the hashing function generates a hash “bucket” number and the hash bucket numbers are mapped to AMPs 116. Range partitioning is a partitioning scheme in which each AMP 116 manages the records falling within a range of values, wherein the entire data set is divided into as many ranges as there are AMPs 116. No partitioning means that a single AMP 116 manages all of the records.

[0024] Generally, the PDEs 112, PEs 114, and AMPs 116 are tangibly embodied in and/or accessible from a device, media, carrier, or signal, such as RAM, ROM, one or more of the DSUs 106, and/or a remote system or device communicating with the computer system 100 via one or more of the DCUs 108. The PDEs 112, PEs 114, and AMPs 116 each comprise logic and/or data which, when executed, invoked, and/or interpreted by the PUs 102 of the computer system 100, cause the methods or elements of the present invention to be performed.

[0025] As noted above, many different hardware and software environments may be used to implement the methods described herein. A spectrum of embodiments ranging from stand alone processors with a single storage device, to multiple distributed processors with distributed storage devices storing one or more databases may be used in various embodiments.

[0026] Horizontal Partial Covering Method

[0027] In FIG. 2, a computer implemented method 200 includes obtaining a query referring to rows in a relational database at 210. A sparse index of the database that has a set of rows that is a subset of the rows referred to in the query is obtained at 220. At 230, rows referred to in the query that are not in the sparse index are obtained. A union of such rows and the rows of the sparse index is performed at 240 to obtain a complete row set for processing the query. In one embodiment, the query may be processed against the union of rows at 250.

[0028] In a further embodiment as illustrated in FIG. 3, a computer implemented method 300 is performed to rewrite a query to provide query results in a more efficient manner. The query is first obtained at 310 and refers to rows in a relational database. At 320, the query is rewritten to select rows from a sparse index. At 330, rows that are not in the sparse index are retrieved and at 340 a union of such rows and the rows of the sparse index is performed to obtain a complete row set for processing the query.

[0029] In one example embodiment, base tables are defined with a partitioned primary index (PPI) by which new incoming data go to the most recent partition(s) as described in the following database definition language (DDL) statements:

[0030]

CREATE SET TABLE orders
(
o_orderkey INTEGER NOT NULL,
o_orderdate DATE FORMAT ‘yyyy-mm-dd’ NOT NULL,
o_ amount integer)
PRIMARY INDEX ( o_orderkey )
PARTITION BY RANGE_N(o_orderdate BETWEEN DATE ‘1998-01-01’
AND DATE ‘2004-12-31’ EACH INTERVAL ‘1’ MONTH );

[0031] The last two lines correspond to a very specific example. In further embodiments, the statements may be represented generically as:

[0032] PARTITION BY RANGE_N(o_orderdate BETWEEN DATE ‘xxx’

[0033] AND DATE ‘yyy’ EACH INTERVAL ‘zzz’ QQQ)

[0034] wherein xxx and yyy are dates, and zzz is a number of time periods QQQ. As indicated above, the dates are in one specific format, but may be in other formats as desired. While a MONTH is indicated as the time period above, the time period may be varied to correspond to an actual application, such as a day, week, year, quarter, hour, minute, or whatever other type of time period desired.

[0035] A join index may be defined with the sparse condition that specifies a “snapshot view” of the data. When the base table is updated, the join index (JI) maintenance may be bypassed as a result of the values of the updated rows being outside the range set by the sparse condition.

• [0036] CREATE JOIN INDEX orders_ji AS
• [0037] SEL o_orderkey, o_orderdate, o_amount
• [0038] FROM orders
• [0039] WHERE o_orderdate BETWEEN DATE ‘2003-01-01’ AND DATE ‘2004-10-31’
• [0040] PRIMARY INDEX (o_orderkey)
• [0041] PARTITION BY range_n(o_orderdate BETWEEN DATE ‘1998-01-01’
• [0042] AND DATE ‘2004-10-31’ EACH INTERVAL ‘1’ MONTH);
• [0043] EXPLAIN INS INTO orders (100, ‘2004-11-01’, 1000);
  • [0044] 1) First, perform an INSERT into HONG.orders.
  • [0045] →No rows are returned to the user as the result of statement 1.
• [0046] EXPLAIN DEL orders WHERE o_orderdate<‘2003-01-01’;
  • [0047] 1) First, lock a distinct HONG.“pseudo table” for write on a RowHash to prevent global deadlock for HONG.orders.
  • [0048] 2) Next, lock HONG.orders for write.
  • [0049] 3) Perform an all-AMPs DELETE from 60 partitions of HONG.orders with a condition of (“HONG.orders.o_orderdate<DATE ‘2003-01-01’”).
  • [0050] 4) Finally, send out an END TRANSACTION step to all AMPs involved in processing the request.
  • [0051]  No rows are returned to the user as the result of statement 1.

[0052] This “snapshot ji” can be used to answer queries that ask for more rows than those included in the JI. For example, the following query

• • [0053] SEL *
  • [0054] FROM orders
  • [0055] WHERE o_orderdate BETWEEN DATE ‘2002-01-01’ AND DATE ‘2004-12-31’;
    can be rewritten as:
  • [0056] SEL *
  • [0057] FROM
  • [0058] (SEL *
  • [0059] FROM orders_ji
  • [0060] WHERE ji_ret_cond
  • [0061] UNION ALL
  • [0062] SEL *
  • [0063] FROM orders
  • [0064] WHERE base_ret_cond)DT;

[0065] Assume that the sparse condition in the JI definition and the query condition are sparse_ji_cond and query_cond, respectively. The ji_ret_cond, which represents the condition used for the join index retrieval, is calculated as:
ji_ret_cond=query_cond AND sparse_ji_cond

[0066] Since all the rows in the join index already satisfy the sparse_ji_cond, the expression can be simplified as:
ji_ret_cond=query_cond

[0067] Furthermore, when
!query_cond AND sparse_ji_cond=false;
i.e. the row set of the query result is a superset of the row set included in the join index, ji_ret_cond may be set to be true because all the rows in the join index are needed to answer the query. In the above example,

• [0068] query_cond=o_orderdate BETWEEN DATE ‘2002-01-01’ AND DATE ‘2004-12-31’;
• [0069] sparse_ji_cond=o_orderdate BETWEEN DATE ‘2003-01-01’ AND DATE ‘2004-10-31’;
  Since

[0070] $\hspace{1em}\begin{array}{c}!\mathrm{query\_cond}\mathrm{AND}\mathrm{sparse\_ji}\mathrm{\_cond}=(\mathrm{o\_orderdate}<‘2002\text{-}01\text{-}01’\mathrm{OR}\\ \mathrm{o\_orderdate}>‘2004\text{-}12\text{-}31’)\mathrm{AND}\\ (\mathrm{o\_orderdate}>=‘2003\text{-}01\text{-}01’\mathrm{AND}\\ \mathrm{o\_orderdate}<=‘2004\text{-}10\text{-}31’)\\ =(\mathrm{o\_orderdate}<‘2002\text{-}01\text{-}01’\mathrm{AND}\\ \mathrm{o\_orderdate}>=‘2003\text{-}01\text{-}01’\mathrm{AND}\\ \mathrm{o\_orderdate}<=‘2004\text{-}10\text{-}31’)\mathrm{OR}\\ (\mathrm{o\_orderdate}>‘2004\text{-}12\text{-}31’\mathrm{AND}\\ \mathrm{o\_orderdate}>=‘2003\text{-}01\text{-}01’\mathrm{AND}\\ \mathrm{o\_orderdate}<=‘2004\text{-}10\text{-}31’)\\ =\mathrm{false}\end{array}$

[0071] Therefore, ji_ret_cond=true in this example.

[0072] The base_ret_cond, which represents the condition for the retrieval from the base table to get the extra rows needed in the query, is calculated as:
base_ret_cond=query_cond AND !sparse_ji_cond
Since

[0073] $\hspace{1em}\begin{array}{c}\mathrm{query\_cond}\mathrm{AND}!\mathrm{sparse\_ji}\mathrm{\_cond}=(\mathrm{o\_orderdate}>=‘2002\text{-}01\text{-}01’\mathrm{AND}\\ \mathrm{o\_orderdate}<=‘2004\text{-}12\text{-}31’)\mathrm{AND}\\ (\mathrm{o\_orderdate}<‘2003\text{-}01\text{-}01’\mathrm{OR}\\ \mathrm{o\_orderdate}>‘2004\text{-}10\text{-}31’)\\ =(\mathrm{o\_orderdate}>=‘2002\text{-}01\text{-}01’\mathrm{AND}\\ \mathrm{o\_orderdate}<=‘2004\text{-}12\text{-}31’)\mathrm{AND}\\ \mathrm{o\_orderdate}<‘2003\text{-}01\text{-}01’\mathrm{OR}\\ (\mathrm{o\_orderdate}>=‘2002\text{-}01\text{-}01’\mathrm{AND}\\ \mathrm{o\_orderdate}<=‘2004\text{-}12\text{-}31’\mathrm{AND}\\ \mathrm{o\_orderdate}>‘2004\text{-}10\text{-}31’)\\ =(\mathrm{o\_orderdate}>=‘2002\text{-}01\text{-}01’\mathrm{AND}\\ \mathrm{o\_orderdate}<‘2003\text{-}01\text{-}01’)\mathrm{OR}\\ (\mathrm{o\_orderdate}>‘2004\text{-}10\text{-}31’\mathrm{AND}\\ \mathrm{o\_orderdate}<=‘2004\text{-}12\text{-}31’)\end{array}$

[0074] Therefore base_ret_cond specifies two range conditions that correspond to the rows that are required in the query but are not included in the join index.

[0075] The above example illustrates the idea of the “horizontal partial covering”—when the row set in JI is a subset of that required by the query, a retrieval to the base table for the rest of rows is needed and the union of the two can give the row set required in the query.

[0076] In the following, an example is described where using the horizontal partial covering method can help to improve performance by leveraging an aggregate join index (AJI) with aggregates at the same or lower level than that is required in the query. Assume a fact table and a dimension table as:

• [0077] Sales (store_id, day_id, prod_id, amount);
• [0078] Calendar (day_id, wk, mth, qtr, yr) unique index(day_id);

[0079] An AJI at week level is defined as:

• [0080] CREATE JOIN INDEX AJI_wk AS
• [0081] SEL wk, mth, SUM(amount) AS wktotalsales
• [0082] FROM sales, calendar
• [0083] WHERE sales.day_id = calender.day_id AND
  • [0084] wk BETWEEN startweek AND endweek
• [0085] GROUP BY wk, mth
• [0086] PRIMARY INDEX (wk)
• [0087] PARTITION BY RANGE_N(wk BETWEEN startweek
• [0088] AND endweek EACH INTERVAL ‘1’ WEEK);

[0089] A query that rolls up to the month level,

• [0090] SEL mth, SUM(amount)
• [0091] FROM sales, calendar
• [0092] WHERE sales.day_id=calender.day_id AND mth BETWEEN startmonth AND endmonth;
• [0093] can be answered by the following rewritten query:
• [0094] SEL mth, SUM (mthtotalsales)
• [0095] FROM
  • [0096] (SEL mth, SUM(wktotalsales) AS mthtotalsales
  • [0097] FROM AJI_wk
  • [0098] WHERE mth BETWEEN startmonth AND endmonth
  • [0099] GROUP BY mth
  • [0100] UNION ALL
  • [0101] SEL mth, SUM(amount) AS mthtotalsales
  • [0102] FROM sales, calendar
  • [0103] WHERE sales.day_id=calender.day_id and
    • [0104] (mth>=startmonth and mth<=endmonth and wk<startweek) OR
    • [0105] (mth>=startmonth and mth<=endmonth and wk>endweek)
  • [0106] GROUsP BY mth) DT (month, mthtotalsales)
• [0107] GROUP BY mth;

[0108] The time ranges covered in the join index (from startweek to endweek) and in the query (from startmonth to endmonth) may be different. So going back to the base table to get the missing rows in the join index may be needed in order to use the AJI to answer the query. A time line 400 in FIG. 4 illustrates that the join index time line covers the query range on the left side but falls short on the right. A portion of data in the first week that are in the startmonth are indicated at 410. Rows that are not included in the join index but required in the query are indicated at 420. By adding the query condition to the join index retrieval, the portion of data in the 1^st week corresponding to the startmonth in the query is selected. This can be done because mth is included in the join index's grouping key. On the other hand, those rows that satisfy the base_ret_cond are fetched from the Calendar table, joined with the Sales table and rolled up to the month level. Note that a final SUM step is added on top of the UNION. The final SUM step is used because there can be overlapping rows returned from the two retrievals. For example, in the time line shown in the diagram, both the roll-ups from the 13^th and 14^th week in the join index and the rows fetched from the base table correspond to the endmonth. One final aggregate is added to merge the subtotals for the same grouping key.

[0109] Maintaining Join Index

[0110] In an ADW environment, to avoid maintaining the join index at real time when the base table is frequently updated, users can define a “snapshot join index” by using the sparse condition in the join index definition. For example, for an orders table as previously defined and a join index defined with a range sparse condition doesn't need to be maintained when the values of the o_orderdate column in the updated rows are outside the range set by the previously defined condition.

[0111] As more data are loaded into and/or purged from the base table, the join index evolves accordingly. Otherwise, the “snapshot join index” may miss a large portion of data that are included in the base table so that the snapshot join index no longer helps to answer the query efficiently.

[0112] A syntax can be used to modify the database definition language (DDL) of a join index when a new scope of data needs to be defined for the “snapshot”. There is no need to drop the join index and recreate one with the new definition, in which case the whole join index table is recalculated. The new sparse condition may be compared in the new DDL with the old one. An incremental part may be found between the two. The JI rows may be calculated from the rows in the base table that satisfy the delta condition, and the JI table may be updated.

[0113] The new syntax may be designed as follows:

• [0114] ALTER JOIN INDEX ji_name CHANGE FROM
• [0115] WHERE old_sparse condition
• [0116] TO
• [0117] WHERE new_sparse condition;

[0118] The syntax specifies the new sparse condition while all the other elements of the join index definition, such as select list, joins, grouping keys etc., remain the same.

[0119] By using this new join index DDL, users have the control of when to update the join index table. Users may choose a batch window to run the update that minimizes the impact to other activities in the ADW. Users may also choose the extent to which they would like to bring the join index up-to-date. The more data that are updated, the bigger the batch window and the less frequent the update is needed.

[0120] In one embodiment, the execution process of the above JI DDL is illustrated in FIG. 5 at 500. At 510, the table description of JI is updated. At 520, spools that contain the old rows to be deleted and the new rows to be inserted, respectively are generated. The spools are then merged into/merge deleted from the existing join index table at 530.

[0121] Generation of the spools at 520 may be performed in different manners. In one embodiment, spools are generated for a single table join index. The same order table example as above is used to illustrate such generation. If it is desired to expand orders_ji to include the most recent two months' data. A new DDL of doing so is:

• [0122] ALTER JOIN INDEX orders_ji CHANGE FROM
• [0123] WHERE o_orderdate BETWEEN DATE ‘2003-01-01’ AND DATE ‘2004-10-31’
• [0124] TO
• [0125] WHERE o_orderdate BETWEEN DATE ‘2003-01-01’ AND DATE ‘2004-12-31’;

[0126] Then the query used to generate the spool that contains the new rows for the JI should be:

• [0127] SEL o_orderkey, o_orderdate, o_amount
• [0128] FROM orders
• [0129] WHERE o_orderdate>‘2004-10-31’ AND o_orderdate<=‘2004-12-31’;

[0130] The syntax is designed in a broad sense that it can be used both to expand JI to include new data and to purge old data that are no longer needed in JI. Therefore in general, two spools will be generated. The WHERE clause condition used to generate the one for deleting the old rows is:
! new_sparse condition AND old_sparse condition
And the WHERE clause condition used to generate the one for adding the new rows is:
new_sparse condition AND !old_sparse condition

[0131] For a multiple table join index, an assumption is made that a fact table and a dimension table are defined as:

• [0132] Sales (store_id, day_id, prod_id, amount);
• [0133] Calendar (day_id, wk, mth, qtr, yr) unique index(day_id);
• [0134] An AJI at week level is defined as:
• [0135] CREATE JOIN INDEX AJI_wk AS
• [0136] SEL wk, mth, SUM(amount) AS wktotalsales
• [0137] FROM sales, calendar
• [0138] WHERE sales.day_id=calender.day_id AND
  • [0139] wk BETWEEN startweek AND endweek
• [0140] GROUP BY wk, mth
• [0141] PRIMARY INDEX (wk)
• [0142] PARTITION BY RANGE_N(wk BETWEEN startweek
• [0143] AND endweek EACH INTERVAL ‘1’ WEEK);

[0144] The time range included in this AJI may be changed by issuing the following DDL command:

• [0145] ALTER JOIN INDEX AJI_wk CHANGE FROM
• [0146] WHERE wk BETWEEN startweek AND endweek
• [0147] TO
• [0148] WHERE wk BETWEEN new_startweek AND new_endweek

[0149] Depending on the relationship between the new and old startweek/endweek, there are different scenarios of changing the AJI:

• • [0150] (i) new_startweek>startweek: purging old historical data from JI;
  • [0151] (ii) new_startweek<startweek: expanding JI to include more historical data;
  • [0152] (iii) new_endweek>endweek: expanding JI to include more recent data;
  • [0153] (iv) new_endweek<endweek: purging recent data from JI.

[0154] Considering the workload in an ADW, scenarios (i) and (iii) are the most useful ones. SQL statements may be used to generate the two spools under such conditions (new_startweek>startweek and new_endweek>endweek):

• [0155] (a) Spool that contains the rows to be deleted from the AJI:
  • [0156] SEL wk, mth, SUM(amount) AS wktotalsales
  • [0157] FROM sales, calendar
  • [0158] WHERE sales.day_id=calender.day_id AND
    • [0159] sales.day_id BETWEEN 1^st day of startweek AND (1^st day of new_startweek-1)
  • [0160] GROUP BY wk, mth;
• [0161] (b) Spool that contains the rows to be inserted into the AJI:
  • [0162] SEL wk, mth, SUM(amount) AS wktotalsales
  • [0163] FROM sales, calendar
  • [0164] WHERE sales.day_id = calender.day_id AND
    • [0165] sales.day_id BETWEEN (Last day of endweek+1) AND Last day of new_endweek
  • [0166] GROUP BY wk, mth;

[0167] When the base table is partitioned on day_id, the retrieval from the sales table is very efficient as the partition elimination is applied to get only those partitions involved in the incremental parts. Also if the join index table is partitioned on wk, the operations of merge delete from and merge into the join index table can benefit from the clustering of the data rows on one or more data blocks that are to be written.

[0168] To some extent, the new syntax is similar to
ALTER TABLE table_name ADD/DROP RANGE BETWEEN . . . ;

[0169] When such a DDL is issued to a base table, the new partitions corresponding to the ADD RANGE expression are added and old partitions corresponding to the DROP RANGE expression are dropped. The new syntax for altering join index DDLs is designed to achieve the same goal of supporting data evolutions in an ADW environment but with the following different aspects:

• • [0170] (1) The ALTER JOIN INDEX syntax is more general. It supports both PPI and non-PPI join indexes and any partition expressions in PPI JI;
  • [0171] (2) DROP RANGE may not be allowed on a join index when the range is not empty. Otherwise, data in the join index may be out of sync with the base table. By changing the sparse condition of the join index, the data in the join index may be manipulated to tailor it for the query requirements. The sparse condition in the join index lets it to be frozen at a certain time frame without being updated frequently along with the base table therefore the maintenance cost of the join index can be reduced significantly. Then changing the sparse condition brings the join index data up-to-date to whatever data freshness requirement that is needed.
  • [0172] (3) The underlying maintenance process of the join index table for the ALTER JOIN INDEX DDL can be every efficient when there are proper PPIs defined for the base table and the join index so that the “snapshot join index” can be brought up-to-date in a small time window.

[0173] FIG. 6 is a flowchart describing a method of updating a join index table generally at 600. At 610, a snapshot join index is defined using a sparse condition in a join index definition. A new sparse condition of the snapshot join index is compared with an old sparse condition at 620. At 630, rows are identified in a base table as a function of the comparing and then the join index table is updated at 640. In one embodiment, the join index table is an aggregate join index table and identifying rows 630 further includes calculating aggregates.

[0174] Conclusion

[0175] A new DDL syntax may be used to change the sparse condition in a join index enabling users to have the control of when to bring the join index up to date and what range of data to include in the join index. When the join index definition is altered, the differences between the old and new data sets are calculated and two spools are generated to merge delete from/merge into the join index table. It provides a way to emulate the performance of the deferred maintenance in some RDBMS systems while guarantees 100% accurate query results.

[0176] The Abstract is provided to comply with 37 C.F.R. §1.72(b) to allow the reader to quickly ascertain the nature and gist of the technical disclosure. The Abstract is submitted with the understanding that it will not be used to interpret or limit the scope or meaning of the claims.