Database Query Optimization via Visible Data Set Limiting

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In three-tier database applications, excessive data retrieval often occurs due to the lack of consideration for the limited number of data sets visible on user interfaces, leading to increased network traffic and memory utilization, especially on mobile devices where only a small subset of data is needed for display.

Innovation Solution

A method is implemented where the request for data sets is modified based on the number of data sets visible in the user interface, using a database cursor to limit the data retrieved, thereby reducing network traffic and memory usage by only accessing and transferring necessary data, and utilizing 'reverse select' to optimize SQL select statements for efficient data transfer.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If the application retrieves all data sets from the database without modification, then complete data availability is achieved, but network traffic and memory utilization increase excessively

Engineering Contradiction:
Improvedata availabilityVSAvoidnetwork traffic
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The patent extracts only the necessary subset of data sets from the database that can be displayed on the user interface. By determining the number of visible data sets and modifying the request accordingly, the system extracts precisely the amount of data needed, eliminating unnecessary network traffic while ensuring all displayable data is available.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent applies partial action by retrieving only a portion of the total data sets from the database - specifically, the number of data sets that can be visible on the user interface. This partial retrieval approach avoids the excessive action of fetching all data sets, thereby reducing network traffic while maintaining sufficient data availability for display purposes.

Inventive Principle:
Principle #16Partial or excessive action

2Reliability

If the application retrieves all data sets from the database without modification, then complete data availability is achieved, but memory utilization increases excessively

Engineering Contradiction:
Improvedata availabilityVSAvoidmemory utilization
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

The patent extracts only the necessary subset of data sets from the database that can be displayed on the user interface. By determining the number of visible data sets and modifying the request accordingly, the system extracts precisely the amount of data needed, eliminating unnecessary memory consumption while ensuring all displayable data is available.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent applies partial action by retrieving only a portion of the total data sets from the database - specifically, the number of data sets that can be visible on the user interface. This partial retrieval approach avoids the excessive action of fetching all data sets, thereby reducing memory utilization while maintaining sufficient data availability for display purposes.

Inventive Principle:
Principle #16Partial or excessive action

3Reliability

If the user interface displays more data sets than its visible capacity, then data completeness is improved, but display efficiency and user experience deteriorate

Engineering Contradiction:
Improvedata completenessVSAvoiddisplay efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent changes the parameter of data set quantity by determining the number of visible data sets based on user interface display capacity. This parameter adjustment ensures that the retrieved data matches the display capabilities, optimizing display efficiency while maintaining data completeness within the visible constraints of the interface.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS9594811B2Method and system for limiting database access results
Publication Date: 2017.03.14 SAP SE
  • US9594811B2 patent drawing
  • US9594811B2 patent drawing
  • US9594811B2 patent drawing

AI summary

A method includes generating a request for data sets in a database via a user interface, modifying the request as a function of a number, n, of data sets visible in the user interface, sending the modified request to the database for execution, and receiving n data sets from the database responsive to the modified request to display on the user interface.