US 11,734,308 B2
Autonomous caching for views
Matthew Dombroski, Lancaster, MA (US); Anne Murphy, Cambridge, MA (US); Ekrem S.C. Soylemez, Lexington, MA (US); and James Hartsing, Nashua, NH (US)
Assigned to Oracle International Corporation, Redwood Shores, CA (US)
Filed by Oracle International Corporation, Redwood Shores, CA (US)
Filed on Mar. 19, 2020, as Appl. No. 16/824,541.
Claims priority of provisional application 62/899,604, filed on Sep. 12, 2019.
Prior Publication US 2021/0081434 A1, Mar. 18, 2021
Int. Cl. G06F 16/27 (2019.01); G06F 16/25 (2019.01); G06F 16/28 (2019.01)
CPC G06F 16/275 (2019.01) [G06F 16/254 (2019.01); G06F 16/282 (2019.01)] 20 Claims
OG exemplary drawing
 
1. A method comprising:
storing query log data comprising a plurality of entries, each entry (1) corresponding to a query in a plurality of queries that were executed against a database and (2) indicating a tuple comprising a set of hierarchy levels corresponding to a set of dimensions;
identifying a plurality of tuples indicated in the query log data;
for each tuple in the plurality of tuples:
identifying a set of entries, from the plurality of entries, that indicate said each tuple and associating the set of entries with said each tuple;
generating aggregated performance data for said each tuple based on performance data associated with a query corresponding to each entry in the set of entries that is associated with said each tuple;
wherein a particular tuple in the plurality of tuples is associated with multiple entries from the plurality of entries;
wherein particular aggregated performance data for the particular tuple is based on (i) first performance data associated with a first query in the multiple entries and (ii) second performance data associated with a second query in the multiple queries;
based on the aggregated performance data, determining at least one of:
whether to create a first auto-cache table associated with said each tuple, or
whether to delete a second auto-cache table associated with said each tuple;
wherein an auto-cache table is created by aggregating data from one or more underlying fact tables used by a view for which the auto-cache table is created;
wherein the method is performed by one or more computing devices.