Pre-Grant Publication Number: 20070124317
Collaborate on the process of community review for this application. Posting will not be forwarded to the USPTO.
Flagging a post as an ACTION ITEM signals further research. Flagging SPAM and ABUSE helps to manage discussion.
Placing double brackets around a reference to a claim or prior art will create a hyperlink to the original
ex. [[claim 1]] and [[prior art 2]].
Please review the Community Code of Conduct prior to posting
Facilitator's Comment 
Action Item Show without Noise
Unfortunately, I'm also struggling with how to nail down the demonstration that the claims are common. It may be that the way the claims are worded is overly broad. For example, transforming data between formats of two data structures can be done in many different ways in a database, including using an externally linked view, an XML fetch, a procedural language call or aliasing columns in a SQL statement. Does the patent intend to claim to cover these techniques?
The other part that I'm getting myself tangled about is that the claims seem to represent the problem and not the solution. The problem is that there are two separate data structures and data needs to move between then. There is an enablement requirement to patents, which I believe this fails. I submit that my ten years of experience make me at least somewhat skilled in the art, yet I cannot tell you how to duplicate the solution.
I'm an expert at database development and how to accomplish what this patent claims, but I have zero training on how to document that via prior art, which is why I've never submitted any. To me, finding prior art for this application's claims are like showing prior art that 1=1. Non-patentability of mathematical formulas aside, 1=1 is so obvious that without training on how to do it, you don't know how to start.
But, this pilot is what it is. Perhaps I can pull something out of an old textbook that demostrates how to do these things.
It shares that property with hierarchical storage management, as previously suggested by Paul McKenney; however, HSM traditionally accesses past (historical) or rarely visited current data, whereas this submission discusses access to what is effectively future data of the primary data store.
(sorry, my original comment was truncated despite being under the stated 100 word max)
Integrated system and method of data warehousing and delivery
US Patent Issued on July 14, 2020
United States Patent 5781911.
There are many methods implemented to try to improve the efficiency of queries within these applications, but I would have to research as to wether there is a similar process al
a) page 4, second column, from first paragraph to the end of the page. This basically describes how to associate data structures with one another. This definition implies a query to one data structure based to provide data based on criteria defined.
b) page 3, section "What is dynamic rollup" and page 4, first column section "Remote Access Benefits" - describing the process of finding the most appropriate data source based on the definition as in a), and in respect to the user's query. Further, page 3, last section titled "HOLAP Logging" briefly describing the capability to refine the data structure based on previous queries.
Note that this paper describes an approach to configuration of a technology, since improved and now marketed as (afaik) "SAS OLAP Server". Hope this helps.
Patrick