The patent badge is an abbreviated version of the USPTO patent document. The patent badge does contain a link to the full patent document.
The patent badge is an abbreviated version of the USPTO patent document. The patent badge covers the following: Patent number, Date patent was issued, Date patent was filed, Title of the patent, Applicant, Inventor, Assignee, Attorney firm, Primary examiner, Assistant examiner, CPCs, and Abstract. The patent badge does contain a link to the full patent document (in Adobe Acrobat format, aka pdf). To download or print any patent click here.
Patent No.:
Date of Patent:
Aug. 07, 2007
Filed:
Mar. 08, 2004
Conor J. Cunningham, Redmond, WA (US);
Eric N. Hanson, Bellevue, WA (US);
Milind M. Joshi, Redmond, WA (US);
Cesar A. Galindo-legaria, Redmond, WA (US);
Florian M. Waas, Seattle, WA (US);
Conor J. Cunningham, Redmond, WA (US);
Eric N. Hanson, Bellevue, WA (US);
Milind M. Joshi, Redmond, WA (US);
Cesar A. Galindo-Legaria, Redmond, WA (US);
Florian M. Waas, Seattle, WA (US);
Microsoft Corporation, Redmond, WA (US);
Abstract
Indexed views or materialized views are used as a secondary index on a base table with multi-valued attributes. This provides for using the index to search in the nested data. Moreover, indexing is provided on the result of an unnest operation. Indexing a view on the result of an unnesting operation provides the ability to index the contents of a nested collection. One such unnesting operation is 'cross apply unnest'. This provides additional options for a query execution plan, leading to a more optimized query. A back-join is provided from the indexed view to the base table to allow fields from the base table that are not present in the indexed view to be included in a result of a query on the table which is processed using the indexed view as an access path. This provides a means of including columns in the query result that are not in the indexed view but are in the base table. The back-join is supported from a single-table indexed view to the base table via a unique clustering key which acts as a logical row locator. Thus, the system can back-join to the base table from an indexed view via the unique clustering key. These features allow the use of indexed views to index a table on the contents of multi-set or multi-valued attributes.