SQL Endpoint Routing for Database Security

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Data analysts face challenges when directly accessing a centralized database managed by an application server, as database object names and structures are unstable, objects may not exist or be outdated, and direct access bypasses security mechanisms, leading to issues with data type mapping and session variables.

Innovation Solution

A method is introduced to route Structured Query Language (SQL) statements through an application server using a SQL endpoint, with design-time configured SQL handlers and service bindings to manage data access, ensuring security and stability by generating SQL service artifacts and parsing statements for authorized data retrieval.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If data analysts directly access the centralized database using SQL statements, then they can use SQL directly without logging into the application server, but they bypass security mechanisms and access unstable database objects

Engineering Contradiction:
ImproveDirect SQL accessVSAvoidSecurity and object stability
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The patent introduces a database link as an intermediary component that connects the centralized database to the application server. This link allows SQL statements to be routed through the application server infrastructure while maintaining secure access controls and object stability. The database link acts as a mediator that enables direct SQL access functionality while preserving the security mechanisms and object management capabilities of the application server.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Stability of the object's composition

If database objects are managed by the application server with zero downtime upgrades, then data stability is maintained, but object names and internal structures become unstable

Engineering Contradiction:
ImproveData availability during upgradesVSAvoidObject name and structure stability
Core Design Contradiction:
Stability of the object's compositionVSAdaptability or versatility

Solution Approach 1:

The patent creates a virtual copy or representation of the centralized database objects through the database link interface. Instead of directly accessing the physical database objects whose names and structures may change during upgrades, users access virtual representations that maintain stable naming conventions. The application server maintains a mapping between the stable virtual object names and the actual database objects, allowing zero downtime upgrades while preserving object name stability for users.

Inventive Principle:
Principle #26Copying

3Adaptability or versatility

If multiple databases are maintained within the same organization, then data accessibility is improved, but maintenance difficulties increase

Engineering Contradiction:
ImproveData accessibilityVSAvoidMaintenance complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent merges multiple database access points into a single unified interface through the application server. Instead of maintaining separate access mechanisms for each database, the database link technology combines them into one standardized access method. Users access all databases through the same SQL interface and authentication mechanism, eliminating the need to maintain multiple separate database connections and reducing overall system maintenance complexity while preserving data accessibility across multiple databases.

Inventive Principle:
Principle #5Merging (Combining)

Data Source

PatentUS11941142B2Dedicated SQL services for cross-system SQL access to an application-server-managed database
Publication Date: 2024.03.26 SAP SE
  • US11941142B2 patent drawing
  • US11941142B2 patent drawing
  • US11941142B2 patent drawing

AI summary

Methods for using SQL statements to access an application-server-managed database are disclosed herein. In some embodiments, a user sends, either directly or indirectly (i.e., remotely) a SQL statement from an ODBC application or server, respectively, to an application server that preprocesses SQL statements for accessing data from a centralized database. The application server may have a SQL endpoint, and access to the SQL endpoint may be determined by a user's logon credentials, a user's presentation of a SAML token, or a user's presentation of a valid certificate. The application server may then parse the SQL statement and determine the user's authorization to access certain objects in the centralized database based on a SQL handler design-time configuration. A result from the statement may be sent back to the user either directly or indirectly and exposed.