Database Audit Metadata Porting Across Server Instances

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current database audit systems face challenges in segregating audit data, configuring audits for specific purposes, and porting audits across database server instances, leading to complexity and potential errors.

Innovation Solution

The solution involves creating multiple audits that can be independently configured and isolated, with audit metadata stored separately from the database server instance, allowing for easy porting and hierarchical audit configuration, enabling audits to be expressed using a data definition language for precise control over audit events.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If audit configuration metadata is stored with the database server instance, then the audit system maintains centralized control, but it becomes complex and error-prone to move databases between server instances

Engineering Contradiction:
Improvedatabase portingVSAvoidaudit configuration management
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The patent extracts audit configuration metadata from the database server instance and stores it separately in the database itself. This separation allows the database to be moved between server instances without carrying complex audit configuration management, while the metadata travels with the database automatically.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent creates a copy of the audit configuration metadata within the database structure, allowing it to be transported with the database to different server instances. This eliminates the need for manual configuration transfer and reduces errors during database porting.

Inventive Principle:
Principle #26Copying

2Measurement precision

If global audit configuration is applied to the entire database, then all accesses are uniformly audited, but it creates overly verbose audit records and lacks precision for specific audit needs

Engineering Contradiction:
Improveaudit scope precisionVSAvoidaudit record volume
Core Design Contradiction:
Measurement precisionVSQuantity of substance

Solution Approach 1:

The patent segments the database into hierarchical levels (database level, schema level, object level) and allows audit configuration to be applied at each level independently. This enables precise targeting of audit scopes and reduces unnecessary audit record generation by only auditing specific objects or schemas when needed.

Inventive Principle:
Principle #1Segmentation

3Adaptability or versatility

If multiple audits are configured for different purposes, then specific audit requirements can be met, but it becomes difficult to tell what purpose each audit fulfills

Engineering Contradiction:
Improveaudit configuration flexibilityVSAvoidaudit configuration management
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces an intermediary layer of audit configuration metadata that acts as a mediator between multiple audit requirements. This metadata structure organizes and labels different audit configurations, making it easier to understand and manage the purpose of each audit without reducing flexibility.

Inventive Principle:
Principle #24Intermediary (Mediator)

4Measurement precision

If programmers must encode what data accesses should be audited, then precise audit control is achieved, but it makes configuration difficult and requires programming expertise

Engineering Contradiction:
Improveaudit control precisionVSAvoidaudit configuration ease
Core Design Contradiction:
Measurement precisionVSEase of operation

Solution Approach 1:

The patent enables self-service audit configuration through metadata that can be defined and managed without requiring programming expertise. The system provides tools and interfaces that allow users to configure audits through declarative metadata rather than encoding, achieving precise control while improving ease of operation.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS8069148B2Configuration of multiple database audits
Publication Date: 2011.11.29 MICROSOFT TECHNOLOGY LICENSING LLC
  • US8069148B2 patent drawing
  • US8069148B2 patent drawing
  • US8069148B2 patent drawing

AI summary

Various technologies and techniques are disclosed for improving configuration of database audits. Multiple audits can be created for a database. Any one of the audits can be turned off without impacting an operation of any remaining audits. Database audits can be ported from one database server instance to another. Database audit metadata is stored in a database separately from a database server instance to which the database is attached. The database can be detached from the database server instance and attached to a second database server instance, with the database audit metadata moving along with the database automatically. Any audits associated with the database audit metadata are automatically activated for the second database server instance. Database audits can be configured using a hierarchical model.