Selective Database Copying for Testing via File Type Filtering
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing database copying technologies are inefficient as they often require copying entire databases, including unnecessary files and change logs, which wastes time and computing resources, especially in enterprise-level systems where a significant portion of data is unstructured and not needed for testing or other purposes.
Innovation Solution
The solution allows users to selectively copy data by specifying which file types to include or exclude, using custom logic and default settings, and includes options for partial copies that omit unnecessary files and change logs, thereby reducing the data volume copied.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a full copy of the database is made, then all data is available for testing, but the copying time and computing resources increase significantly
Solution Approach 1:
The database copy operation is segmented into selective copying of only necessary tables and data. The system identifies and copies only the specific tables required for testing purposes, excluding unnecessary tables, files, and change logs, thereby reducing copying time while maintaining adequate data availability for testing.
Solution Approach 2:
The patent extracts only the essential data components needed for testing from the entire database. By identifying and extracting only necessary tables and data while excluding unnecessary files and change logs, the system reduces the data volume to be copied, thus decreasing copying time and resource consumption.
2Reliability
If a full copy of the database is made, then all data is available for testing, but the computing resources consumed increase significantly
Solution Approach 1:
The database copy operation is segmented into selective copying of only necessary tables and data. The system identifies and copies only the specific tables required for testing purposes, excluding unnecessary tables, files, and change logs, thereby reducing computing resources while maintaining adequate data availability for testing.
Solution Approach 2:
The patent extracts only the essential data components needed for testing from the entire database. By identifying and extracting only necessary tables and data while excluding unnecessary files and change logs, the system reduces the data volume to be copied, thus decreasing computing resources and energy consumption.
3Reliability
If unnecessary files and change logs are included in the copy, then data completeness is maintained, but the data volume and copying complexity increase
Solution Approach 1:
The patent extracts only the essential data components needed for testing from the entire database. By identifying and extracting only necessary tables and data while excluding unnecessary files and change logs, the system reduces the data volume to be copied, thus decreasing computing resources and energy consumption.
Solution Approach 2:
Instead of copying the entire database, the system performs a partial copy including only the necessary tables and data required for testing. This partial action approach reduces data volume and copying complexity while maintaining adequate data completeness for testing purposes.
Data Source
AI summary
Techniques and solutions are described for copying data from a source client to a target client. It may be selected, such as by a user, whether a full copy or a partial copy of a set of source client data should be made. If a partial copy is selected, a set of file types is provided. The file types can be used to define files that should be included in, or excluded from, the copy. A data source of the source client is analyzed to determine data associated with a file type that is to be included in a copy, or is associated with a file type that is not indicated as to be excluded from the copy. The determined data is copied from the source client to the target client.