CN115185930B - IT monitoring system migration method - Google Patents

IT monitoring system migration method Download PDF

Info

Publication number
CN115185930B
CN115185930B CN202211108003.8A CN202211108003A CN115185930B CN 115185930 B CN115185930 B CN 115185930B CN 202211108003 A CN202211108003 A CN 202211108003A CN 115185930 B CN115185930 B CN 115185930B
Authority
CN
China
Prior art keywords
migration
data
distribution
strategy
monitoring system
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
CN202211108003.8A
Other languages
Chinese (zh)
Other versions
CN115185930A (en
Inventor
张庭厚
肖良华
林志鹏
陈夏
杨果
邓嘉怡
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Shanghai Data Center of China Life Insurance Co Ltd
Original Assignee
Shanghai Data Center of China Life Insurance Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Shanghai Data Center of China Life Insurance Co Ltd filed Critical Shanghai Data Center of China Life Insurance Co Ltd
Priority to CN202211108003.8A priority Critical patent/CN115185930B/en
Publication of CN115185930A publication Critical patent/CN115185930A/en
Application granted granted Critical
Publication of CN115185930B publication Critical patent/CN115185930B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/21Design, administration or maintenance of databases
    • G06F16/214Database migration support
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/22Indexing; Data structures therefor; Storage structures
    • G06F16/2282Tablespace storage structures; Management thereof
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/27Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
    • YGENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02DCLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D10/00Energy efficient computing, e.g. low power processors, power management or thermal management

Landscapes

  • Engineering & Computer Science (AREA)
  • Databases & Information Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Data Mining & Analysis (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Software Systems (AREA)
  • Computing Systems (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)

Abstract

The invention relates to an IT monitoring system migration method, which comprises the following steps: various base table lists in the IT monitoring system are combed, and base table types are determined based on the updating frequency of the base tables; aiming at the distribution table, confirming a distribution column of the distribution table based on a distribution column selection strategy, and dividing and confirming data storage duration, a partition and a data hot and cold strategy based on IT monitoring data characteristics and an application scene; constructing a migration information table based on the type of the base table and the related information of the distribution table; migrating the migration information table to a target database; adjusting program adaptation database drive; and making a data hierarchical migration strategy and migrating according to the migration strategy. The invention can realize the migration from the centralized database to the distributed database and stably and efficiently operate the IT monitoring system on the trusted distributed database.

Description

IT monitoring system migration method
Technical Field
The invention relates to the technical field of IT monitoring, in particular to an IT monitoring system migration method.
Background
Under the background of foreign technology banning and national security requirement strengthening, the innovation ecology rapidly develops, and a plurality of excellent innovation localization software and hardware appear in the market. In order to meet the IT reform development requirements of enterprises, the IT monitoring system needs to be subjected to innovation, migration and transformation.
The TBase is an HTAP distributed database cluster maintained by the Tencent cloud database team. The TBase is an enterprise-level HTAP distributed database cluster product which is high in expansibility, SQL compatibility (compatible with most PostgreSQL grammars and most Oracle grammars), provides distributed global transaction consistency function support, has multi-level disaster tolerance capability and multi-dimensional resource isolation capability, is high in safety, obtains multiple international and national certifications, and is widely applied to multiple industries. The TBase adopts a distributed cluster architecture, the nodes are correspondingly independent in a share nothing (share nothing) mode, the data of the nodes are processed respectively, the processed results can be gathered to an upper layer or can flow among the nodes, all processing units are communicated through a network protocol, and the parallel processing and expansion capability is better. The original monitoring configuration data and performance data adopt a centralized database, so that how to stably and efficiently operate the IT monitoring system on the trusted distributed database becomes an urgent problem to be solved.
Disclosure of Invention
The technical problem to be solved by the invention is to provide an IT monitoring system migration method, which can realize the migration from a centralized database to a distributed database and stably and efficiently operate the IT monitoring system on a trusted distributed database.
The technical scheme adopted by the invention for solving the technical problems is as follows: the IT monitoring system migration method comprises the following steps:
various base table lists in the IT monitoring system are combed, and base table types are determined based on the updating frequency of the base tables, wherein the base table types comprise a copy table and a distribution table;
for the distribution table, confirming a distribution column of the distribution table based on a distribution column selection strategy, and dividing and confirming data storage duration, partitions and a data hot and cold strategy based on IT monitoring data characteristics and application scenes;
constructing a migration information table based on the type of the base table and the related information of the distribution table;
migrating the migration information table to a target database;
adjusting program adaptation database drive;
making a data grading migration strategy and migrating according to the migration strategy; the data hierarchical migration strategy comprises the following steps: the method comprises the steps of configuration data full migration, alarm data full migration, performance data aggregation and migration after and temporary data non-migration.
The determining of the type of the base table based on the update frequency of the base table specifically comprises the following steps: and comparing the updating frequency of the base table with an updating threshold, if the updating frequency of the base table is less than the updating threshold, determining the base table as a copy table, otherwise, determining the base table as a distribution table.
The method for determining the data storage duration, the partition and the data hot and cold strategy based on the IT monitoring data characteristics and the application scene specifically comprises the following steps: dividing the IT monitoring data into: configuring data, alarm data, performance data and temporary data, establishing corresponding partitions, comparing the storage duration of the monitoring data with a time threshold, if the storage duration exceeds the time threshold, adopting a cold separation strategy for the monitoring data, and otherwise, adopting a hot separation strategy for the monitoring data.
The migrating the migration information table to the target database specifically includes: and the compiling table structure migration module reads the migration information table, inquires the structure and the index of the migration information table, and completes the construction of a new table and the index in the target database based on the corresponding relation of the field type mapping table.
The basic strategy of the table structure migration module is as follows: if the main key exists, selecting the main key as a distribution key; when the main key is a compound field combination, selecting fields with more field value selectivity as distribution keys or splicing the compound fields into a new field to be used as the distribution keys; if the primary key does not exist, the UUID is used as a distribution key; the columns of the variation values are not taken as distribution columns; the external key only has the effect of internal constraint of the same node, and the external key field and the corresponding main key field are distribution keys of each table; when a plurality of unique indexes are used, a unique index not including a distribution column needs to be added to the distribution column.
When the adjusting program is matched with the database drive, adjusting the distribution column into a non-distribution column field for updating; and when the distribution column cannot be replaced by a non-distribution column field, deleting and then inserting.
The configuration data full migration refers to automatically reading in configuration according to the migration information table, retrieving and writing configuration data in the migration information table, and automatically checking the number of records after writing is completed; the alarm data full migration refers to automatic reading configuration according to the migration information table, retrieving and writing the alarm data in the migration information table, and automatically checking the number of records after the writing is finished; the performance data is collected and then migrated, namely, according to the automatic read-in configuration of the migration information table, the performance data in the migration information table is retrieved according to time, and is collected according to hours, and is written after being collected, and the collection number and the original library record number are automatically checked after the writing is finished.
The IT monitoring system migration method further comprises the step of establishing read-write separation, wherein the step of establishing read-write separation is to utilize the backup data node to establish a read-only plane and provide data for a downstream system to use.
Advantageous effects
Due to the adoption of the technical scheme, compared with the prior art, the invention has the following advantages and positive effects: according to the invention, different table types are selected according to the data volume and the read-write characteristics of the IT monitoring configuration table and the time increment table, so that the data interaction overhead among data nodes is reduced, and the query performance is improved. The invention establishes a data strategy based on the characteristics and application scenes of the monitoring data, and ensures the lasting stability of the system performance through partitioning, convergence and cold and hot areas. According to the invention, based on the characteristics and application scenes of the monitoring data, a migration strategy is defined, historical data are selected to be collected first and then migrated, so that the migration efficiency is improved, and real-time data are guaranteed by bidirectional pushing of a new acquisition system and an old acquisition system during the track combination. The invention establishes read-write separation, fully uses the standby machine resources and improves the overall performance of the system.
Drawings
FIG. 1 is a flow chart of an embodiment of the present invention.
Detailed Description
The invention will be further illustrated with reference to the following specific examples. It should be understood that these examples are for illustrative purposes only and are not intended to limit the scope of the present invention. Further, it should be understood that various changes or modifications of the present invention can be made by those skilled in the art after reading the teaching of the present invention, and these equivalents also fall within the scope of the claims appended to the present application.
The embodiment of the invention relates to an IT monitoring system migration method, which can be applied to the migration construction of an IT basic platform monitoring system of a data center IT of a large insurance company, and aims at the IT monitoring system based on a centralized database to realize efficient migration to a distributed database and efficient and stable operation by formulating a data strategy, a base table type strategy, table structure redesign, read-write separation and the like. The Tbase distributed database is taken as an example for detailed description, and as shown in fig. 1, the method specifically includes the following steps:
step S01: and (4) combing various base table lists of the IT monitoring system, and clearly monitoring a configuration table and a time increment table. The method is based on a selection strategy of the base table type (a copy table and a distribution table), the base table with low updating frequency is created into a copy table, and the copy table comprises a personnel information table, an equipment information table, an application system table, a virtual operation and maintenance group, a Hosts \ Templates \ Items \ discovery rule and the like. The table with high updating frequency is created into a distribution table, and comprises an alarm table Alert, a historical alarm table Arch _ Alert, an Event table Event, message sending tables Messages, auditLog, a performance data real-time History and a performance data convergence trends. At this point a migration information table (see table 1) may be constructed.
Table 1: tbase _ in _ tables
table_name tab_old type shard_key part part_key part_range hot_cold migrate
Name of table Old base table Watch type Distribution row Partition table Partition column Extent of partition Cold and hot zones Migration type
hosts Y replica full
employees Y replica full
events Y shard -
alerts Y shard full
history Y shard full
trends N shard aggregate
According to the embodiment, different table types are selected according to the data volume and the read-write characteristics of the IT monitoring configuration table and the time increment table, the data interaction overhead among data nodes is reduced, and the query performance is improved.
Step S02: for the distribution table base table, its distribution column is validated based on a distribution column selection policy. Taking Event table Event as an example, id is used as distribution list to make it be distributed on each data node uniformly, and clock:: timestamp is used as partition key. The migration information table (see table 2) is updated based on the above.
Table 2: tbase _ in _ tables
table_name tab_old type shard_key part part_key part_range hot_cold migrate
Table name Old library table Watch type Distribution row Partition table Partition column Extent of partition Cold and hot zones Migration type
hosts Y replica - N - - full
employees Y replica - N - - full
events Y shard id Y clock month -
alerts Y shard id Y clock month full
history Y shard id Y clock day full
trends N shard id Y clock month aggregate
Step S03: and dividing and confirming data storage duration, partitions and data hot and cold strategies based on IT monitoring data characteristics and application scenes. The monitoring data can be basically divided into four types: configuring data, alarm data, performance data (real-time, trend), temporary data (log record, message record, source event and the like), establishing corresponding partitions according to the partition types, adopting a cold separation strategy if the storage time of the data exceeds 1 year, or adopting a hot separation strategy, namely migrating cold nodes by the data before 1 year, and regularly cleaning the expired data of the hot nodes. And updating the migration information table to obtain a complete migration information table (see table 3).
Table 3: tbase _ in _ tables
table_name tab_old type shard_key part part_key part_range hot_cold migrate
Table name Old base table Watch type Distribution row Partition table Partition column Extent of partition Cold and hot zones Migration type
hosts Y replica - N - - - full
employees Y replica - N - - - full
events Y shard id Y clock month - -
alerts Y shard id Y clock month Y full
history Y shard id Y clock day - full
trends N shard id Y clock month Y aggregate
The embodiment establishes a data strategy based on the characteristics and application scenes of the monitoring data, and ensures the lasting stability of the system performance through partitioning, convergence and cold and hot areas.
Step S04: the base table structure is migrated. And the compiling table structure migration module reads the migration information table, inquires the original table structure and the index, and completes the construction of a new table and the index based on the corresponding relation in the field type mapping table in the Tbase. And (4) finishing verification: the number of columns and indexes of the source table and the target table are compared.
Wherein the basic policy of the table structure migration module is: if the primary key (the uniqueness index) exists, selecting the primary key as a distribution key; when the main key is a composite field combination, selecting fields with more field value selectivity as a distribution key or splicing the composite fields into a new field to be used as the distribution key; if there is no primary key, then UUID can be used as the distribution key; the distribution column cannot perform updating, and thus the column of the variation value cannot be regarded as the distribution column; the foreign key only has the effect of constraint in the same node, and the foreign key field and the corresponding primary key field need to be the distribution key of each table, otherwise, the data distribution in different nodes can cause update failure. When a plurality of unique indexes are used, the unique indexes of the distribution column are not included, the distribution column needs to be added, or the unique check is completed by other modes of the program. The distributed database can be adapted through the design of the table structure, and the advantages of the distributed database are fully utilized.
Step S05: and (6) program adaptation. (1) adjusting a program to adapt to a database driver; (2) The distribution column update problem, the distribution column selection of the adjusting base table; when a distribution column cannot be replaced with another library table column, delete is first followed by insert. In the step, for the syntax problem of the full-field update of a part of programs, the update of a distribution column is removed, or the distribution column is changed into a deleteAndInsert mode, and the programs are adapted and modified in the above way, so that the database is driven to update and upgrade to adapt to the Tbase version.
Step S06: making a data hierarchical migration strategy: the method comprises the steps of configuration data full migration, alarm data full migration, performance data aggregation and migration, and temporary data non-migration.
Step S06-1: and configuring the full-scale migration of data. And the extraction and writing module automatically reads in configuration according to the tbase _ in _ tables table, retrieves and writes the configuration data of the original table, and automatically checks the record number of records after the writing is finished.
Step S06-2: and migrating the alarm data in full. And the extraction and writing module automatically reads in configuration according to the tbase _ in _ tables table, retrieves and writes the alarm data of the original table, and automatically checks the record number of records after the writing is finished.
Step S06-3: and (5) converging and extracting the performance data. And an extraction, aggregation (aggregation value max-min-avg and aggregation number) and writing module automatically reads configuration according to the tbase _ in _ tables, retrieves the performance data of the original table according to time, aggregates the performance data according to hours, writes the performance data after aggregation, and automatically checks the aggregation number and the original library records number after writing.
The historical performance data are gathered and then migrated, and the data are gathered in hours based on the characteristics of the monitoring data and the use scene of the monitoring data to form trend data (maximum value, minimum value and average value), so that the migration efficiency is improved.
Step S07: and establishing read-write separation. A read-only plane is built by using the standby data nodes, data are provided for a downstream system to use, standby machine resources are fully used in the mode, and the overall performance of the system is improved.
According to the invention, different table types are selected according to the data volume and the read-write characteristics of the IT monitoring configuration table and the time increment table, so that the data interaction overhead among data nodes is reduced, and the query performance is improved. The invention establishes a data strategy based on the characteristics and application scenes of the monitoring data, and ensures the lasting stability of the system performance through partitioning, gathering and cold and hot areas. According to the method and the system, a migration strategy is defined based on the characteristics and application scenes of the monitoring data, historical data are selected to be collected first and then migrated, migration efficiency is improved, and real-time data are guaranteed by bidirectional pushing of a new acquisition system and an old acquisition system during the track combination period. The invention establishes read-write separation, fully uses the standby machine resources and improves the overall performance of the system.

Claims (7)

1. An IT monitoring system migration method is characterized by comprising the following steps:
various base table lists in the IT monitoring system are combed, and base table types are determined based on the updating frequency of the base tables, wherein the base table types comprise a copy table and a distribution table;
aiming at the distribution table, confirming a distribution column of the distribution table based on a distribution column selection strategy, and dividing and confirming data storage duration, a partition and a data hot and cold strategy based on IT monitoring data characteristics and an application scene; the method for determining the data storage duration, the partition and the data hot and cold strategy based on the IT monitoring data characteristics and the application scene specifically comprises the following steps: dividing the IT monitoring data into: configuring data, alarm data, performance data and temporary data, establishing corresponding partitions, comparing the storage duration of the monitoring data with a time threshold, if the storage duration exceeds the time threshold, adopting a cold separation strategy for the monitoring data, and otherwise, adopting a hot separation strategy for the monitoring data;
constructing a migration information table based on the type of the base table and the related information of the distribution table;
migrating the migration information table to a target database;
adjusting program adaptation database drive;
making a data hierarchical migration strategy and migrating according to the migration strategy; the data hierarchical migration strategy comprises the following steps: the method comprises the steps of configuration data full migration, alarm data full migration, performance data aggregation and migration after and temporary data non-migration.
2. The IT monitoring system migration method according to claim 1, wherein the determining of the type of the base table based on the update frequency of the base table is specifically: and comparing the updating frequency of the base table with an updating threshold, if the updating frequency of the base table is less than the updating threshold, determining the base table as a replication table, otherwise, determining the base table as a distribution table.
3. The IT monitoring system migration method according to claim 1, wherein the migrating the migration information table to a target database specifically comprises: and the compiling table structure migration module reads the migration information table, inquires the structure and the index of the migration information table, and completes the construction of a new table and the index in the target database based on the corresponding relation of the field type mapping table.
4. The IT monitoring system migration method according to claim 3, wherein the basic policy of the table structure migration module is: if the main key exists, selecting the main key as a distribution key; when the main key is a compound field combination, selecting fields with more field value selectivity as distribution keys or splicing the compound fields into a new field to be used as the distribution keys; if the primary key does not exist, the UUID is used as a distribution key; the columns of the variation values are not taken as distribution columns; the external key only has the effect of internal constraint of the same node, and the external key field and the corresponding main key field are distribution keys of each table; when a plurality of unique indexes are provided, a unique index not including a distribution column needs to be added to the distribution column.
5. The IT monitoring system migration method according to claim 1, wherein when the adjustment program adapts to a database driver, the distribution column is adjusted to a non-distribution column field for updating; and when the distribution column cannot be replaced by a non-distribution column field, deleting and then inserting.
6. The IT monitoring system migration method according to claim 1, wherein the configuration data full migration is to automatically read in configuration according to the migration information table, retrieve and write configuration data in the migration information table, and automatically check the number of records after the writing is completed; the alarm data full migration refers to that according to the migration information table, automatic read-in configuration is performed, alarm data in the migration information table are retrieved and written, and after the writing is completed, the number of records is automatically checked; the performance data is collected and then migrated, namely, according to the automatic read-in configuration of the migration information table, the performance data in the migration information table is retrieved according to time, and is collected according to hours, and is written after being collected, and the collection number and the original library record number are automatically checked after the writing is finished.
7. The IT monitoring system migration method according to claim 1, further comprising establishing read-write separation, wherein the establishing read-write separation means that a read-only plane is established by using a backup data node, and data is provided for a downstream system to use.
CN202211108003.8A 2022-09-13 2022-09-13 IT monitoring system migration method Active CN115185930B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202211108003.8A CN115185930B (en) 2022-09-13 2022-09-13 IT monitoring system migration method

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202211108003.8A CN115185930B (en) 2022-09-13 2022-09-13 IT monitoring system migration method

Publications (2)

Publication Number Publication Date
CN115185930A CN115185930A (en) 2022-10-14
CN115185930B true CN115185930B (en) 2022-12-06

Family

ID=83524501

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202211108003.8A Active CN115185930B (en) 2022-09-13 2022-09-13 IT monitoring system migration method

Country Status (1)

Country Link
CN (1) CN115185930B (en)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107357883A (en) * 2017-06-30 2017-11-17 北京奇虎科技有限公司 Data migration method and device
US10108645B1 (en) * 2015-12-30 2018-10-23 EMC IP Holding Company LLC Database monitoring for online migration optimization
CN112783859A (en) * 2021-01-08 2021-05-11 河北志晟信息技术股份有限公司 Lightweight concurrent migration method for database
CN114048188A (en) * 2021-11-16 2022-02-15 金现代信息产业股份有限公司 Cross-database data migration system and method
CN114415965A (en) * 2022-01-25 2022-04-29 中国农业银行股份有限公司 Data migration method, device, equipment and storage medium

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9805108B2 (en) * 2010-12-23 2017-10-31 Mongodb, Inc. Large distributed database clustering systems and methods

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10108645B1 (en) * 2015-12-30 2018-10-23 EMC IP Holding Company LLC Database monitoring for online migration optimization
CN107357883A (en) * 2017-06-30 2017-11-17 北京奇虎科技有限公司 Data migration method and device
CN112783859A (en) * 2021-01-08 2021-05-11 河北志晟信息技术股份有限公司 Lightweight concurrent migration method for database
CN114048188A (en) * 2021-11-16 2022-02-15 金现代信息产业股份有限公司 Cross-database data migration system and method
CN114415965A (en) * 2022-01-25 2022-04-29 中国农业银行股份有限公司 Data migration method, device, equipment and storage medium

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
分布式数据库系统的数据分布策略分析;胡洪云等;《电脑知识与技术》;20210819;全文 *
腾讯云数据库团队;腾讯云数据库团队;《https://cloud.tencent.com/developer/article/1657537》;20200708;全文 *

Also Published As

Publication number Publication date
CN115185930A (en) 2022-10-14

Similar Documents

Publication Publication Date Title
US20220237166A1 (en) Table partitioning within distributed database systems
CN101477486B (en) File backup recovery method based on sector recombination
JP6280872B2 (en) Distributed database with modular blocks and associated log files
US11782649B2 (en) Restoring an archive authorized by an authenticated user
CN113111129B (en) Data synchronization method, device, equipment and storage medium
KR20210135477A (en) Systems and methods for augmenting database applications with blockchain technology
CN105190623A (en) Log record management
CN108509462B (en) Method and device for synchronizing activity transaction table
WO2003009178A2 (en) Database systems, methods and computer program products including primary key and super key indexes for use with partitioned tables
CN106570163B (en) Audit log read-write management method and system facing unreliable environment
US20140330780A1 (en) Universal delta data load
US10108690B1 (en) Rolling subpartition management
CN103605585A (en) Intelligent backup method based on data discovery
US20150006485A1 (en) High Scalability Data Management Techniques for Representing, Editing, and Accessing Data
Kvet et al. Complex time management in databases
US7020656B1 (en) Partition exchange loading technique for fast addition of data to a data warehousing system
CN110659259A (en) Database migration method, server and computer storage medium
CN115185930B (en) IT monitoring system migration method
US10747438B1 (en) Reporting using archived data
CN115964444A (en) Cloud native distributed multi-tenant database implementation method and system
CN111565211B (en) CDN configuration distribution network system
US7043491B1 (en) Partition exchange technique for operating a data warehousing system
CN114328591A (en) Transaction execution method, device, equipment and storage medium
CN111428270A (en) Distributed storage method and system for database based on optical disk
US10747461B1 (en) Updating objects for archived objects

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant