File Data Records from Internal Templates in One Transaction

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Creating new files in a file system database involves multiple database operations, leading to significant processing, storage, and energy overheads due to the use of transactional file systems and multiple locks on the database.

Innovation Solution

Utilizing internal file templates with common attributes for newly created files, allowing the creation of a file data record in a single transaction by copying the template into the file system database, rather than using multiple transactions to write attributes individually.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Manufacturing precision

If multiple database operations are used to create a new file with individual attributes, then the file data record can be fully populated with all necessary attributes, but the processing overhead, storage overhead, and energy consumption increase significantly due to multiple transactions and locks

Engineering Contradiction:

Improvefile data record completenessVSAvoidenergy consumption

Core Design Contradiction:

Manufacturing precisionVSUse of energy by moving object

Solution Approach 1:

The patent pre-creates a template file data record with all common attributes and default values before actual file creation. When a new file is created, the system copies the pre-prepared template and then applies only the unique attributes, avoiding the need to create and populate all attributes through multiple transactions from scratch.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The patent merges multiple database operations into a single transaction by copying the entire template file data record in one atomic operation. This combines the creation of the file data record structure and the population of common attributes into a single unified operation, reducing the number of transactions from multiple to one.

Inventive Principle:

Principle #5Merging (Combining)

2Manufacturing precision

If multiple database operations are used to create a new file with individual attributes, then all file attributes can be set correctly, but the transaction log size and data storage requirements increase due to multiple undo and redo record pairs

Engineering Contradiction:

Improvefile attribute accuracyVSAvoidtransaction log data

Core Design Contradiction:

Manufacturing precisionVSQuantity of substance

Solution Approach 1:

The template file data record is prepared in advance with all common attributes and default values already set. This preliminary preparation means that during actual file creation, only the unique attributes need to be applied, reducing the amount of data that needs to be logged in undo and redo records.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The patent extracts the common attributes and default values into a separate template file data record. This extraction allows the system to reuse the template for all files with common attributes, eliminating the need to re-log these common attributes in each transaction, thereby reducing transaction log size.

Inventive Principle:

Principle #2Taking out (Extraction)

3Reliability

If multiple locks are applied on the file system database for each attribute write operation, then data consistency can be maintained, but the processor usage and operational overhead increase

Engineering Contradiction:

Improvedata consistencyVSAvoidlock management complexity

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The patent combines multiple attribute write operations into a single template copy operation. By copying the entire template file data record in one atomic transaction, the system reduces the number of locks from multiple individual attribute locks to a single lock for the template copy operation, simplifying lock management while maintaining data consistency.

Inventive Principle:

Principle #5Merging (Combining)

4Manufacturing precision

If individual attribute writes are performed using multiple transactions, then each attribute can be written with proper validation, but the file creation time and processing duration increase

Engineering Contradiction:

Improveattribute validationVSAvoidfile creation time

Core Design Contradiction:

Manufacturing precisionVSLoss of time

Solution Approach 1:

The template file data record is prepared in advance with all common attributes and default values already validated and set. This preliminary validation means that during actual file creation, the system only needs to copy the template and apply unique attributes, significantly reducing the validation and processing time compared to validating and writing each attribute individually through multiple transactions.

Inventive Principle:

Principle #10Preliminary action

Data Source

PatentUS20250231911A1Creating a file data record based on an internal file template

Publication Date: 2025.07.17 MICROSOFT TECHNOLOGY LICENSING LLC

AI summary

Methods, systems, and computer program products for creating a file system file data record based on an internal file template. A computer system identifies an application programming interface (API) request to create a new file. Based at least on identifying the API request, the computer system determines a set of attributes associated with the new file. The computer system also identifies a selected file template, from among a set of file templates, that is associated with the set of attributes. The computer system creates a file data record for the new file within a file system database, including inserting a copy of the selected file template into the file data record for the new file.