Enterprise Reporting Capabilities In Storage Management Systems

US2016098462A1 · US · A1

Patent metadata
FieldValue
Publication numberUS-2016098462-A1
Application numberUS-201414507409-A
CountryUS
Kind codeA1
Filing dateOct 6, 2014
Priority dateOct 6, 2014
Publication dateApr 7, 2016
Grant date

How to read this patent

A practical reading order for non-experts. Skip the full description unless you need deep technical detail.

  1. Title

    What the patent document calls the invention.

  2. Abstract

    A short plain-language summary of the technical disclosure.

  3. Assignees and inventors

    Who owns or filed the patent and who is credited as inventor.

  4. Key dates

    Filing, priority, publication, and grant dates set the timeline.

  5. First independent claim

    The legal scope of protection — read this for what is actually claimed.

  6. CPC / IPC classifications

    Technology tags used to group this patent with similar filings.

  7. Citations and related patents

    Prior art links and similar publications in this corpus.

Abstract

Official abstract text for this publication.

A method of refreshing a materialized view includes creating a materialized view based on a first result of a database query executed against a set of tables stored in a database and discovering a set of child storage objects associated with a parent storage object. The method also includes inserting, based on discovering the set of child storage objects, an entry into one or more tables of the set of tables, the entry including a child storage object of the set of child storage objects. The method further includes delaying a refresh of the materialized view until after the entry is inserted into the set of tables and then refreshing the materialized view, which is based on a second result of the database query executed against the set of tables.

First claim

Opening claim text (preview).

What is claimed is: 1 . A method of refreshing a materialized view, comprising: creating a first materialized view based on a first result of a database query executed against a set of tables stored in a database; discovering a set of child storage objects associated with a parent storage object; inserting, based on the discovering a set of child storage objects, an entry into one or more tables of the set of tables, the entry including a child storage object of the set of child storage objects; delaying a refresh of the first materialized view until after the entry is inserted into the one or more tables of the set of tables; and after the entry is inserted into the one or more tables of the set of tables, refreshing the first materialized view to determine a second materialized view, the second materialized view being based on a second result of the database query executed against the set of tables. 2 . The method of claim 1 , further including: discovering the parent storage object. 3 . The method of claim 2 , further including: inserting, based on the discovering the parent storage object, a second entry into one or more tables of the set of tables, the second entry including the parent storage object. 4 . The method of claim 1 , wherein the first materialized view is different from the second materialized view. 5 . The method of claim 1 , wherein the parent storage object and set of child storage objects are based on a hierarchy, and the parent storage object contains the set of child storage objects. 6 . The method of claim 1 , wherein the discovering a set of child storage objects includes discovering a last child storage object of the set of child storage objects, and wherein the entry includes the last child storage object, the method further including: identifying a materialized view update timestamp for the second materialized view, the materialized view update timestamp indicating a last update time of the second materialized view; identifying an update timestamp of one or more tables of the set of tables, an update timestamp of a given table indicating a last update time of the given table; comparing the materialized view update timestamp to the update timestamp of one or more tables of the set of tables; and determining, based on the comparing, whether to refresh the second materialized view. 7 . The method of claim 6 , wherein the comparing includes determining whether the materialized view update timestamp is earlier than the update timestamp of the one or more tables of the set of tables, wherein in response to determining that the materialized view update timestamp is later than each update timestamp of the set of tables, determining to not refresh the second materialized view. 8 . The method of claim 7 , wherein in response to determining that the materialized view update timestamp is earlier than an update timestamp of the set of tables, determining to refresh the second materialized view. 9 . The method of claim 6 , further including: in response to determining to refresh the second materialized view, refreshing the second materialized view to determine a third materialized view; submitting a second database query to the third materialized view; and generating a report based on a result of the second database query. 10 . The method of claim 9 , further including: in response to determining to not refresh the second materialized view, submitting a second database query to the second materialized view; and generating a report based on a result of the second database query. 11 . The method of claim 10 , further including: receiving a request for the report. 12 . A computing device comprising: a memory containing machine readable medium comprising machine executable code having stored thereon instructions for performing a method of refreshing a materialized view; and a processor coupled to the memory, the processor configured to execute the machine executable code to: update, based on discovering a last child storage object associated with a parent storage object, a set of tables stored in a database; create a materialized view based on a result of a database query executed against the set of tables stored in the database; compare a materialized view update timestamp to an update timestamp of one or more tables of the set of tables, wherein the materialized view update timestamp indicates a last update time of a first materialized view and an update timestamp of a given table indicates a last update time of the given table; delay a refresh of the first materialized view until after the last child storage object has been discovered; and refresh the first materialized view to determine a second materialized view when the last child storage object is discovered, wherein the second materialized view is based on one or more tables affected by the discovery of the last child storage object. 13 . The system of claim 12 , wherein the system monitoring tool persists a discovery of a parent storage object and a set of child storage objects associated with the parent storage object to the database. 14 . The system of claim 12 , wherein the system monitoring tool spawns one or more monitors to discover child storage objects associated with the parent storage object. 15 . The system of claim 12 , wherein the system monitoring tool determines whether the materialized view update timestamp is earlier than an update timestamp of the set of tables, wherein in response to determining that the materialized view update timestamp is later than each update timestamp of the set of tables, the system monitoring tool determines to not refresh the second materialized view, and wherein in response to determining that the materialized view update timestamp is earlier than an update timestamp of the set of tables, the system monitoring tool determines to refresh the second materialized view to determine a third materialized view 16 . The system of claim 12 , wherein the system monitoring tool determines whether the materialized view update timestamp is earlier than the update timestamp of the set of tables, wherein in response to determining that the materialized view update timestamp is earlier than an update timestamp of the set of tables, the system monitoring tool refreshes the materialized view and the reporting tool submits a query to the refreshed materialized view that is based on a second result of the database query executed against the set of tables. 17 . The system of claim 16 , further including: a reporting tool that receives a request for a report that uses data from one or more tables of the set of tables. 18 . The system of claim 17 , wherein responsive to the reporting tool receiving the request, the system monitoring tool compares the materialized view update timestamp to the update timestamp of one or more tables of the set of tables. 19 . The system of claim 17 , wherein the reporting tool submits a second database query to the second materialized view when the materialized view update timestamp is later than each update timestamp of the set of tables and submits the second database query to the third materialized view when the materialized view update timestamp is earlier than an update timestamp of the set of tables. 20 . A non-transitory machine readable medium having stored thereon instructions for performing a method, comprising machine executable code which when executed by at least one machine, causes the machine to: create a firs

Assignees

Inventors

Classifications

Patent family

Related publications grouped by family.

External sources

Frequently asked questions

Answers are generated from the same data shown on this page.

What does patent US2016098462A1 cover?
A method of refreshing a materialized view includes creating a materialized view based on a first result of a database query executed against a set of tables stored in a database and discovering a set of child storage objects associated with a parent storage object. The method also includes inserting, based on discovering the set of child storage objects, an entry into one or more tables of the…
Who is the assignee on this patent?
Netapp Inc
What technology area does this patent fall under?
Primary CPC classification G06F16/248. Mapped technology areas include Physics.
When was this patent published?
Publication date Thu Apr 07 2016 00:00:00 GMT+0000 (Coordinated Universal Time) (A1). Legal status and post-grant events are not shown on this page.
What related patents are in patentsdb?
We list 8 related publications on this page (citations in our corpus or others sharing the same primary CPC).