Database View Copying for Usage Tracking and Migration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Database vendors face challenges in identifying and disseminating information about specific database views used by analytic tools, and in managing customer extensions and modifications, which can lead to time-consuming processes during upgrades and installations.
Innovation Solution
Creating a copy of the vendor view in the customer view layer with a link to the original, allowing changes to be applied only to the copy, enabling tracking and easy migration of modifications, and supporting customer extensions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of information
If vendor views are directly consumed by analytic tools, then the system is simple to operate, but the vendor cannot identify which specific views are being used by customers
Solution Approach 1:
The patent introduces a customer view layer as an intermediary between the vendor view layer and analytic tools. This customer view layer contains customer view definitions that reference vendor views, enabling the system to track which views are being used while maintaining a clear separation of concerns. The intermediary layer captures view usage information without directly modifying the vendor's view definitions.
2Adaptability or versatility
If customers extend and modify vendor views, then the views become more adaptable to customer needs, but managing upgrades and migrations becomes time-consuming
Solution Approach 1:
The patent segments the view system into distinct layers: vendor views, customer views, and analytic tool consumption. Customer extensions are captured as separate customer view definitions that reference vendor views through links. This segmentation allows upgrades to be applied at the vendor view level while customer-specific modifications are preserved in the customer view layer, enabling automated migration processes.
Solution Approach 2:
The system performs preliminary actions by automatically detecting customer view extensions before upgrades occur. The view engine identifies which customer views reference which vendor views, and this information is used to automatically apply migrations during the upgrade process, eliminating manual intervention and reducing migration time.
3Adaptability or versatility
If vendor views are modified to accommodate customer views, then customer needs are met, but the original vendor views lose their standardization and consistency
Solution Approach 1:
The patent creates customer view definitions that are essentially copies or references to vendor views, stored in the customer view layer. These customer views contain links to the original vendor views, allowing customers to have their own customized versions without modifying the original vendor views. This copying mechanism preserves vendor view consistency while enabling customer-specific adaptations.
Data Source
AI summary
Embodiments of methods and systems for database viewing, create a copy of a vendor view in a customer view layer that is present between an interface layer and the database layer. In certain embodiments this copy of the vendor view may contain no customer specific logic, simply serving as a 1:1 projection in the customer view allowing the vendor to track customer access to particular vendor views. According to some embodiments, the copy of the vendor view may be changed to create a modification view. Changes are applied to the modification view only, leaving the original vendor view unchanged with a link to the stored modification copy. This link can be used to adjust the modification copy whenever a hot fix or a new version of the ‘modified’ database content is installed to the customer system. Embodiments may support consumer extensions to the vendor views and/or to the database itself.