Enterprise Table Backup Restoration for Filtering Efficiency

Solution Overview

Problem

Existing multi-tiered enterprise network systems consume significant processing capacity and bandwidth when restoring unfiltered tables after a filtering operation, as they typically regenerate the entire table from scratch.

Innovation Solution

A system and method that detects filtering operations and stores table elements in a backup collection, allowing for efficient restoration of the unfiltered table node from this backup when the filtering function is disabled, thereby avoiding full regeneration.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If the system regenerates the entire table from scratch after filtering, then the unfiltered table is restored, but processing capacity and bandwidth are significantly consumed

Engineering Contradiction:

Improvetable restoration completenessVSAvoidprocessing capacity consumption

Core Design Contradiction:

ReliabilityVSUse of energy by moving object

Solution Approach 1:

The system performs preliminary action by creating and storing a backup copy of the table data before the filtering operation. This backup is then used for restoration after filtering, eliminating the need to regenerate the entire table from scratch and significantly reducing processing capacity consumption during restoration.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The system creates a backup copy of the table data in memory before filtering. This copy is then restored after the filtering operation completes, avoiding the need to regenerate the full table and reducing both processing capacity and bandwidth usage during restoration.

Inventive Principle:

Principle #26Copying

2Reliability

If the system regenerates the entire table from scratch after filtering, then the unfiltered table is restored, but bandwidth usage increases

Engineering Contradiction:

Improvetable restoration completenessVSAvoidbandwidth usage

Core Design Contradiction:

ReliabilityVSLoss of energy

Solution Approach 1:

The system performs preliminary action by creating and storing a backup copy of the table data before the filtering operation. This backup is then used for restoration after filtering, eliminating the need to regenerate the entire table from scratch and significantly reducing processing capacity consumption during restoration.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The system creates a backup copy of the table data in memory before filtering. This copy is then restored after the filtering operation completes, avoiding the need to regenerate the full table and reducing both processing capacity and bandwidth usage during restoration.

Inventive Principle:

Principle #26Copying

3Productivity

If the system stores table elements in a backup collection during filtering, then restoration efficiency improves, but memory usage increases

Engineering Contradiction:

Improverestoration speedVSAvoidmemory consumption

Core Design Contradiction:

ProductivityVSQuantity of substance

Solution Approach 1:

The system performs preliminary action by creating and storing a backup copy of the table data before the filtering operation. This backup is then used for restoration after filtering, eliminating the need to regenerate the entire table from scratch and significantly reducing processing capacity consumption during restoration.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The system creates a backup copy of the table data in memory before filtering. This copy is then restored after the filtering operation completes, avoiding the need to regenerate the full table and reducing both processing capacity and bandwidth usage during restoration.

Inventive Principle:

Principle #26Copying

Data Source

PatentUS7707155B2System and method for efficiently filtering and restoring tables within a multi-tiered enterprise network

Publication Date: 2010.04.27 SAP SE

AI summary

A system and method are described for efficiently filtering and restoring tables within an enterprise application server. For example, one embodiment of the invention detects that a filtering function has been selected for a particular table node and responsively stores elements from the table node within a backup table collection. The filtering function is then performed to generate a filtered table node containing a subset of elements specified by the filtering function. Subsequently, upon detecting that the filtering function has been disabled, the table node may be restored from the backup table collection.