Tenant-Specific Database Segmentation for Multi-Client Systems

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional multi-client server systems face challenges in managing database upgrades, content deployment, and data backup/recovery due to shared databases, leading to increased downtime and reliability issues, while single-client systems require significant client effort and expertise for maintenance.

Innovation Solution

Implementing a system where data structures are designated as tenant-specific, allowing for separate storage and management, enabling providers to host multiple clients with isolated and secure data structures, and using shared data structures stored in a provider space accessible by tenants.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of manufacture

If a multi-client system uses a common database for all clients, then resource sharing and cost efficiency are improved, but database maintenance time and client downtime increase

Engineering Contradiction:
Improveresource sharing efficiencyVSAvoiddatabase maintenance downtime
Core Design Contradiction:
Ease of manufactureVSLoss of time

Solution Approach 1:

The patent segments the common database into tenant-specific databases, where each tenant has their own isolated database instance. This segmentation allows independent maintenance, backup, and recovery operations for each tenant without affecting others, thereby reducing overall maintenance downtime while preserving resource sharing benefits at the platform level.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent extracts tenant-specific data and structures from the common database into separate tenant databases. This extraction enables the provider to use standard database tools for individual tenant operations and allows maintenance activities to be performed on specific tenant databases without impacting the entire system.

Inventive Principle:
Principle #2Taking out (Extraction)

2Ease of manufacture

If a multi-client system uses a common database, then infrastructure cost is reduced, but content deployment time and complexity increase

Engineering Contradiction:
Improveinfrastructure cost efficiencyVSAvoidcontent deployment time
Core Design Contradiction:
Ease of manufactureVSLoss of time

Solution Approach 1:

The patent implements a copying mechanism where tenant-specific databases can be created by copying from template databases or existing tenant databases. This allows rapid content deployment and tenant provisioning without manual setup, reducing deployment time while maintaining cost efficiency through automated database creation and management.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The patent uses pre-configured database templates that contain standard structures, schemas, and initial data. These templates are prepared in advance, allowing new tenant databases to be quickly instantiated by copying and customizing the template, thereby accelerating content deployment while maintaining infrastructure efficiency.

Inventive Principle:
Principle #10Preliminary action

3Device complexity

If a multi-client system uses a common database, then system simplicity is maintained, but data backup and recovery capability deteriorates

Engineering Contradiction:
Improvesystem structural simplicityVSAvoiddata backup and recovery reliability
Core Design Contradiction:
Device complexityVSReliability

Solution Approach 1:

The patent segments data storage into tenant-specific databases while maintaining a unified management interface. This segmentation enables reliable backup and recovery of individual tenant data using standard database tools without requiring complex custom solutions, thereby improving reliability while keeping the management interface simple.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces a database management layer that acts as an intermediary between the simplified user interface and the segmented tenant databases. This intermediary handles the complexity of multi-tenant database management, backup, and recovery operations transparently, allowing users to benefit from both simplicity and reliability.

Inventive Principle:
Principle #24Intermediary (Mediator)

4Reliability

If a single-client system is used for each client, then data isolation and reliability are improved, but client maintenance effort and expertise requirements increase

Engineering Contradiction:
Improvedata isolation securityVSAvoidclient maintenance effort
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The patent implements self-service capabilities where tenants can perform routine maintenance operations on their own databases using standardized tools and interfaces. This reduces the need for provider intervention and client expertise while maintaining data isolation, as tenants can independently manage their own database instances.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The patent provides a universal database management platform that handles multiple functions (creation, maintenance, backup, recovery) for all tenant databases through a single interface. This universality reduces client maintenance effort by consolidating operations that would otherwise require specialized knowledge into standardized, provider-managed processes.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Data Source

PatentUS7680825B2Systems and methods for generating tenant-specific properties for use in a provider-tenant environment
Publication Date: 2010.03.16 SAP SE
  • US7680825B2 patent drawing
  • US7680825B2 patent drawing
  • US7680825B2 patent drawing

AI summary

Exemplary methods and systems may designate a data structure as tenant-specific or shared. By reviewing a plurality of data structures at the provider corresponding to a plurality of tenants, the provider may determine which of the plurality of data structures are specific to a first tenant of the plurality of tenants, and generate a tenant specific designation to identify a data structure as specific to the first tenant. Further, the provider may associate a data structure determined to be specific to the first tenant with the generated tenant specific designation. With this capability a provider-tenant system may separately store each tenants data.