Heterogeneous replication method for database

Abstract

The invention discloses a heterogeneous replication method for a database. The method comprises the following steps: (a) acquiring process data which are generated in an operation process of a relational database; (b) carrying out separation and extraction on session data and customer data in the acquired process data; (c) storing the separated and extracted session data into a non-relational database, wherein the session data stored in the non-relational database are divided according to the session IDs (identity cards), and comprise SQLID (structured query language identity card), transferred application program, time of duration, transferred SQL (structured query language) quantity, wait events and occupied memory size; storing the session data after sorting according to the time order. According to the heterogeneous replication method for the database provided by the invention, through separation of the session data and the customer data, the session data generated in the operation process of the relational database are stored by virtue of an NoSQL format, thus the monitored data can be stored for a long period of time; occupation in a system tablespace is reduced, and subsequent statistic analysis, fault tracking and performance optimization are facilitated.

Description

technical field [0001] The invention relates to a database processing method, in particular to a database heterogeneous replication method. Background technique [0002] The traditional relational database has good performance, high stability, long history, and is easy to use, powerful, and has accumulated a large number of successful cases. [0003] Process data is stored in a table in a relational database, and is associated by a similar sid. For example v$session table and v$process table. In these tables, each record represents a process data. If you want to fully display all the process data of a session, you need to associate these tables for query. [0004] For example, the relational database Oracle, its session information is stored in the dynamic performance view of v$session, and the information in v$session is copied to v$active_session_history every second, and this part of historical data is still stored in memory , and every 10 seconds, the information in ...

AI Technical Summary

Problems solved by technology

Although Oracle comes with this part of the function, because this type of data is big data, it cannot be stored for a long time. If long-term storage is set, it will impose a certain burden on the database system and affect the performance of the database.

[0005] It can be seen from the above that although the relational database is very powerful, it cannot store monitoring data well for a long time, and its scalability is poor (requires complex technology to realize), the IO pressure is high under big data, and it is difficult to change the table structure

Images