CN112162832A - Method and device for realizing audit data storage under multi-version concurrency control - Google Patents
Method and device for realizing audit data storage under multi-version concurrency control Download PDFInfo
- Publication number
- CN112162832A CN112162832A CN202010932428.5A CN202010932428A CN112162832A CN 112162832 A CN112162832 A CN 112162832A CN 202010932428 A CN202010932428 A CN 202010932428A CN 112162832 A CN112162832 A CN 112162832A
- Authority
- CN
- China
- Prior art keywords
- audit data
- tuple
- transaction number
- audit
- database
- 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.)
- Granted
Links
- 238000012550 audit Methods 0.000 title claims abstract description 172
- 238000000034 method Methods 0.000 title claims abstract description 43
- 238000013500 data storage Methods 0.000 title claims abstract description 24
- 230000006399 behavior Effects 0.000 claims description 15
- 238000003780 insertion Methods 0.000 claims description 14
- 230000037431 insertion Effects 0.000 claims description 14
- 230000008569 process Effects 0.000 description 9
- 238000004891 communication Methods 0.000 description 4
- 238000010586 diagram Methods 0.000 description 4
- 230000009471 action Effects 0.000 description 3
- 238000005457 optimization Methods 0.000 description 2
- 238000012545 processing Methods 0.000 description 2
- 230000005540 biological transmission Effects 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/466—Transaction processing
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/50—Monitoring users, programs or devices to maintain the integrity of platforms, e.g. of processors, firmware or operating systems
- G06F21/55—Detecting local intrusion or implementing counter-measures
- G06F21/552—Detecting local intrusion or implementing counter-measures involving long-term monitoring or reporting
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/60—Protecting data
- G06F21/602—Providing cryptographic facilities or services
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Security & Cryptography (AREA)
- Computer Hardware Design (AREA)
- Health & Medical Sciences (AREA)
- Bioethics (AREA)
- General Health & Medical Sciences (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The application provides a method and a device for realizing audit data storage under multi-version concurrent control, wherein the method comprises the following steps: under the condition that the audit data to be inserted exist, a fixed transaction number is adopted as a tuple header to be spliced with the audit data to be inserted to form an audit data tuple; the fixed transaction number is a transaction number already submitted; and storing the audit data tuple in an audit data table in a database. The method provided by the application does not need to apply for the transaction number as in the prior art, so that all fixed connections can see the audit tuples marked by the fixed transaction number, and the corresponding audit data tuples can also be quickly inserted into the audit data table of the database, so that the transactions do not need to be submitted as frequently as in the prior art.
Description
Technical Field
The present disclosure relates to the field of database technologies, and in particular, to a method and an apparatus for implementing audit data storage under multi-version control.
Background
The database audit is the work of recording various database accesses and operations, can provide a basis for event responsibility determination after a security event occurs in the database, and can also give an alarm for the risk behavior of database operation.
The audit data is formed by database audit, and has the following characteristics relative to the common table in the database: (1) audit data cannot be rolled back; (2) audit data can only be added (insert), changed (update) and deleted (delete); (3) the audit data table cannot be deleted (drop) and only can be transferred. Based on the foregoing, audit data needs to be independent of user data, i.e., needs to be stored separately.
At present, on the premise that a multi-version concurrency control mechanism is deployed in a database, if audit data is stored in a data table form in the database, multi-version concurrency control rules need to be followed, and a plurality of transaction numbers need to be occupied and submitted at regular time.
Disclosure of Invention
To solve the above technical problem or at least partially solve the above technical problem, the present disclosure provides a method and an apparatus for implementing audit data storage under multi-version concurrent control.
In one aspect, the present application provides a method for implementing audit data storage under multi-version concurrent control, including:
under the condition that audit data to be inserted exist, a fixed transaction number is adopted as a tuple header to be spliced with the audit data to be inserted to form an audit data tuple; the fixed transaction number is a transaction number already submitted;
and storing the audit data tuple in an audit data table in a database.
Optionally, the splicing is performed with the to-be-inserted audit data by using a fixed transaction number as a tuple header to form an audit data tuple, including:
and calling a tuple read-only insertion interface, and splicing the tuple read-only insertion interface with the audit data to be inserted by using a fixed transaction number as a tuple header to form the audit data tuple.
Optionally, the method further comprises: analyzing the audit data in the audit data table, and judging whether risk behaviors exist or not;
and generating a warning prompt and/or executing a corresponding control operation under the condition of the risk behavior.
Optionally, storing the audit data tuple in an audit data table in a database, including: and storing the audit data in the audit data table by adopting a transparent encryption means.
On the other hand, the application provides a device for realizing audit data storage under multi-version concurrent control, including:
the audit data tuple forming unit is used for splicing the audit data to be inserted by using a fixed transaction number as a tuple head under the condition that the audit data to be inserted exist to form an audit data tuple; the fixed transaction number is a transaction number already submitted;
and the storage unit is used for storing the audit data tuples in an audit data table in a database.
Optionally, the audit data tuple forming unit includes a call tuple read-only insertion interface, and the tuple read-only insertion interface uses a fixed transaction number as a tuple header to be spliced with the audit data to be inserted to form the audit data tuple.
Optionally, the apparatus further comprises: the risk judgment unit is used for analyzing the audit data in the audit data table and judging whether risk behaviors exist or not;
and the warning unit is used for generating a warning prompt and/or executing corresponding control operation under the condition that the risk judgment unit has the risk behavior.
Optionally, the storage unit stores the audit data in the audit data table by adopting a transparent encryption means.
The application also provides a database server, which comprises a processor and a memory;
the processor is operative to perform the steps of the method as previously described by calling programs or instructions stored in the memory.
The present application also provides a computer-readable storage medium storing a program or instructions for causing a computer to perform the steps of the method as described above.
The method and the device for realizing audit data storage under multi-version concurrent control distribute the fixed transaction number submitted for the meaning of the audit data to be inserted, and do not need to apply the transaction number as in the prior art, so that all connections can see the audit data tuple marked by the fixed transaction number, the corresponding audit data tuple can be quickly inserted into the audit data table of the database, and the transaction does not need to be frequently submitted as in the prior art.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present disclosure and together with the description, serve to explain the principles of the disclosure.
In order to more clearly illustrate the embodiments or technical solutions in the prior art of the present disclosure, the drawings used in the description of the embodiments or prior art will be briefly described below, and it is obvious for those skilled in the art that other drawings can be obtained according to the drawings without inventive exercise.
FIG. 1 is a flow chart of a method for implementing audit data storage provided by an embodiment of the present application; (ii) a
FIG. 2 is a schematic structural diagram of an apparatus for implementing audit data storage according to an embodiment of the present application;
FIG. 3 is a schematic structural diagram of a database server provided in an embodiment of the present application;
wherein: 11-judging unit, 12-auditing data tuple forming unit, 13-storage unit, 21-processor, 22-memory, 23-communication interface, 24-bus system.
Detailed Description
In order that the above objects, features and advantages of the present disclosure may be more clearly understood, aspects of the present disclosure will be further described below. It should be noted that the embodiments and features of the embodiments of the present disclosure may be combined with each other without conflict.
In the following description, numerous specific details are set forth in order to provide a thorough understanding of the present disclosure, but the present disclosure may be practiced in other ways than those described herein; it is to be understood that the embodiments disclosed in the specification are only a few embodiments of the present disclosure, and not all embodiments.
The embodiment of the application provides a method for realizing audit data storage under multi-version concurrent control, which is used for realizing rapid storage of audit data in a data table form and reducing resource consumption.
Fig. 1 is a flowchart of a method for implementing audit data storage according to an embodiment of the present application. As shown in FIG. 1, the method provided by the embodiment of the application comprises steps S101-S103.
S101: judging whether audit data to be inserted exist; if yes, executing S102; if not, wait and execute the step again.
In the operation process of the database server, after receiving a database operation statement input by a user and judging that the database operation statement is legal through lexical analysis and grammatical analysis, the database server generates corresponding audit data to be inserted according to the database operation statement. Specifically, the database server may directly use the database operation statement as the audit data to be inserted.
S102: and splicing the fixed transaction number serving as a tuple header with the audit data to be inserted to form an audit data tuple.
In step S102, the fixed transaction number is a transaction number specifically set for storing audit data, and may be represented by committedXid in the database server, which is a transaction number already submitted. The fixed transaction number is different from the transaction number occupied by the tuple operation in the service data table during the multi-version concurrent control, and the commit operation can be independently executed to realize storage.
In step S102, the fixed transaction number is used as the tuple header to be spliced with the audit data to be inserted to form the audit data tuple, and the process is to assign the fixed transaction number to the transaction information of the tuple header and assign the audit data to the data body of the tuple. The audit data tuple formed after the step S102 is executed is temporarily stored in the memory of the database server.
S103: the audit data tuples are stored in an audit data table in a database.
Step S103, storing the audit data tuple in an audit data table, namely submitting the audit data tuple to a storage operation device to realize the process of storing the audit data tuple. Step S103 is executed immediately after the execution of step S102 is completed.
Step S103 can be performed immediately because the fixed transaction number adopted in step S102 is the transaction number that has already been committed, rather than being performed in the form of a transaction number as occupied when operating on a tuple in the service data table.
In step S102, the database server allocates a fixed transaction number to the to-be-inserted audit data, which means that the transaction number has already been submitted, so that there is no need to apply for the transaction number as in the prior art, all connections can see the audit tuple marked by the fixed transaction number, and the corresponding audit data tuple can also be quickly inserted into the audit data table of the database, i.e., there is no need to submit the transaction as frequently as in the prior art.
In a specific application of the embodiment of the present application, step S102 specifically includes: and calling a tuple read-only insertion (tuple _ insert _ ready) interface, and splicing the tuple read-only data insertion interface with the audit data to be inserted by using a fixed transaction number as a tuple head to form the audit data tuple. The tuple read-only insertion interface is a data call interface specially designed for the audit data, and in the interface, a fixed transaction number is directly adopted when a tuple head of the audit data tuple is assigned, and a new transaction number does not need to be applied.
As described above, because the audit data in the embodiment of the present application is stored in the form of a data table, some existing operations for the data table can be directly applied to the audit data table.
In step S103, the audit data tuple is stored in an audit data table in the database, and the audit data can be directly stored in the data table by means of transparent encryption; therefore, the safety of audit data storage can be guaranteed.
In the embodiment of the present application, in addition to the foregoing steps S101 to S103, the data stored in the audit data table may be analyzed, and whether a behavior corresponding to the audit data is a risk behavior is determined; if the behavior corresponding to the audit data is risk behavior, a warning prompt can be generated or corresponding control operation can be executed.
Because the audit data is stored in a data table form, the audit data table can be analyzed by utilizing the query optimization capability of the existing table data, and then the corresponding operation is determined.
Besides providing the foregoing method for implementing audit data storage under multi-version concurrency control, an embodiment of the present application further provides a device for implementing audit data storage under multi-version concurrency control.
Fig. 2 is a schematic structural diagram of an apparatus for implementing audit data storage according to an embodiment of the present application. As shown in fig. 2, the apparatus provided in the embodiment of the present application includes a judging unit 11, an audit data tuple forming unit 12, and a storage unit 13.
The judging unit 11 is used for judging whether audit data to be inserted exist.
The audit data tuple forming unit 12 is configured to splice the to-be-inserted audit data with a fixed transaction number as a tuple header under the condition that the to-be-inserted audit data exists, so as to form an audit data tuple.
In the operation process of the database server, after receiving a database operation statement input by a user and judging that the database operation statement is legal through lexical analysis and grammatical analysis, the database server generates corresponding audit data to be inserted according to the database operation statement. Specifically, the database server may directly use the database operation statement as the audit data to be inserted.
The fixed transaction number is a transaction number specifically set for storing audit data, which may be denoted committedXid in the database server, which is a transaction number that has been committed. The fixed transaction number is different from the transaction number occupied by the tuple operation in the service data table during the multi-version concurrent control, and the commit operation can be independently executed to realize storage.
And the fixed transaction number is used as a tuple header to be spliced with the audit data to be inserted to form an audit data tuple, and the process is to assign the fixed transaction number to the transaction information of the tuple header and assign the audit data to the data body of the tuple. And the audit data tuples formed after execution are temporarily stored in the memory of the database server.
The storage unit 13 is configured to store the audit data tuple in an audit data table in the database. Storing the audit data element group in the audit data table, submitting the audit data element group to a storage operation device, and realizing the process of storing the audit data element group
Since the fixed transaction number is used and is the transaction number that has already been committed, rather than being executed in the form of a transaction number as occupied when operating on a tuple in the service data table, the storage unit 13 can immediately store an operation that audits data tuples.
Because the database server distributes the fixed transaction number which means that the transaction number is already submitted to the to-be-inserted audit data, the transaction number does not need to be applied as in the prior art, all connections can see the audit tuples marked by the fixed transaction number, the corresponding audit data tuples can also be quickly inserted into the audit data table of the database, and the transactions do not need to be submitted as frequently as in the prior art.
In a specific application of the embodiment of the present application, the audit data tuple forming unit 12 includes a tuple read-only insertion (tuple _ insert _ ready) interface, and the tuple read-only data insertion interface uses a fixed transaction number as a tuple header to be spliced with the audit data to be inserted, so as to form an audit data tuple. The tuple read-only insertion interface is a data call interface specially designed for the audit data, and in the interface, a fixed transaction number is directly adopted when a tuple head of the audit data tuple is assigned, and a new transaction number does not need to be applied.
As described above, because the audit data in the embodiment of the present application is stored in the form of a data table, some existing operations for the data table can be directly applied to the audit data table.
In the embodiment of the present application, the storage unit 13 stores the audit data tuple in the audit data table in the database, and can directly store the audit data in the data table by means of transparent encryption; therefore, the safety of audit data storage can be guaranteed.
The device can also comprise a risk judgment unit and an alarm unit besides the audit data tuple forming unit 12 and the storage unit 13.
The risk judgment unit is used for analyzing the audit data in the audit data table and judging whether risk behaviors exist or not; the alarm unit is used for generating a warning prompt and/or executing corresponding control operation under the condition that the risk judgment unit has risk behaviors. Because the audit data is stored by adopting the running of the data table, the audit data table can be analyzed by utilizing the query optimization capability of the existing table data, and then the corresponding operation is determined.
Besides the method and the device, the embodiment of the application also provides a database server for realizing the method for auditing the data storage under the multi-version concurrent control.
Fig. 3 is a schematic structural diagram of a database server according to an embodiment of the present application. As shown in fig. 3, the database server includes: at least one processor 21, at least one memory 22, and at least one communication interface 23. The various components in the electronic device are coupled together by a bus system 24. The communication interface 23 is used for information transmission with an external device. Understandably, the bus system 24 is used to enable connective communication between these components. The bus system 34 includes a power bus, a control bus, and a status signal bus in addition to the data bus. For clarity of illustration, however, the various buses are labeled as bus system 24 in fig. 3.
It will be appreciated that the memory 22 in this embodiment may be either volatile memory or nonvolatile memory, or may include both volatile and nonvolatile memory.
In some embodiments, memory 22 stores elements, executable units or data structures, or a subset thereof, or an expanded set thereof: an operating system and an application program.
The operating system includes various system programs, such as a framework layer, a core library layer, a driver layer, and the like, for implementing various basic tasks and processing hardware-based tasks. The application programs, including various application programs such as a Media Player (Media Player), a Browser (Browser), etc., are used to implement various application tasks. The method and program for realizing audit data storage under the multi-version concurrency control provided by the embodiment of the disclosure can be contained in an application program.
In the embodiment of the present disclosure, the processor 21 is configured to execute the steps of the method for auditing data storage under the multi-version concurrency control provided by the present application by calling a program or an instruction stored in the memory 22, specifically, a program or an instruction stored in an application program.
The processor 31 may be an integrated circuit chip having signal processing capabilities. In implementation, the steps of the above method may be performed by integrated logic circuits of hardware or instructions in the form of software in the processor 21. The Processor 21 may be a general-purpose Processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), an off-the-shelf Programmable Gate Array (FPGA) or other Programmable logic device, a discrete Gate or transistor logic device, or a discrete hardware component. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
The method for realizing audit data storage under multi-version concurrent control provided by the embodiment of the disclosure can be directly embodied as the execution of a hardware decoding processor, or the execution of the hardware decoding processor and a software unit in the decoding processor are combined. The software elements may be located in ram, flash, rom, prom, or eprom, registers, among other storage media that are well known in the art. The storage medium is located in a memory 22, and the processor 21 reads the information in the memory 22 and performs the steps of the method in combination with its hardware.
The embodiments of the present disclosure further provide a non-transitory computer-readable storage medium, where the non-transitory computer-readable storage medium stores a program or an instruction, and the program or the instruction causes a computer to execute the steps of the embodiments of the method for implementing audit data storage under multi-version concurrency control, which are not described herein again to avoid repeated descriptions.
It is noted that, in this document, relational terms such as "first" and "second," and the like, may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other identical elements in a process, method, article, or apparatus that comprises the element.
The foregoing are merely exemplary embodiments of the present disclosure, which enable those skilled in the art to understand or practice the present disclosure. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments without departing from the spirit or scope of the disclosure. Thus, the present disclosure is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.
Claims (10)
1. A method for realizing audit data storage under multi-version concurrent control is characterized by comprising the following steps:
under the condition that audit data to be inserted exist, a fixed transaction number is adopted as a tuple header to be spliced with the audit data to be inserted to form an audit data tuple; the fixed transaction number is a transaction number already submitted;
and storing the audit data tuple in an audit data table in a database.
2. The method of claim 1, wherein the forming an audit data tuple by using a fixed transaction number as a tuple header to be concatenated with the audit data to be inserted comprises:
and calling a tuple read-only insertion interface, and splicing the tuple read-only insertion interface with the audit data to be inserted by using a fixed transaction number as a tuple header to form the audit data tuple.
3. The method of claim 1 or 2, further comprising:
analyzing the audit data in the audit data table, and judging whether risk behaviors exist or not;
and generating a warning prompt and/or executing a corresponding control operation under the condition of the risk behavior.
4. The method of claim 1 or 2, wherein storing the audit data tuple in an audit data table in a database comprises:
and storing the audit data in the audit data table by adopting a transparent encryption means.
5. An apparatus for implementing audit data storage under multi-version concurrent control, comprising:
the audit data tuple forming unit is used for splicing the audit data to be inserted by using a fixed transaction number as a tuple head under the condition that the audit data to be inserted exist to form an audit data tuple; the fixed transaction number is a transaction number already submitted;
and the storage unit is used for storing the audit data tuples in an audit data table in a database.
6. The apparatus of claim 5,
the audit data tuple forming unit comprises a call tuple read-only insertion interface, and the tuple read-only insertion interface adopts a fixed transaction number as a tuple header to be spliced with the audit data to be inserted to form the audit data tuple.
7. The apparatus of claim 5 or 6, further comprising:
the risk judgment unit is used for analyzing the audit data in the audit data table and judging whether risk behaviors exist or not;
and the warning unit is used for generating a warning prompt and/or executing corresponding control operation under the condition that the risk judgment unit has the risk behavior.
8. The apparatus of claim 5 or 6,
the storage unit stores the audit data in the audit data table by adopting a transparent encryption means.
9. A database server comprising a processor and a memory;
the processor is adapted to perform the steps of the method of any one of claims 1 to 4 by calling a program or instructions stored in the memory.
10. A computer-readable storage medium, characterized in that it stores a program or instructions for causing a computer to carry out the steps of the method according to any one of claims 1 to 4.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010932428.5A CN112162832B (en) | 2020-09-08 | 2020-09-08 | Method and device for realizing audit data storage under multi-version concurrency control |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010932428.5A CN112162832B (en) | 2020-09-08 | 2020-09-08 | Method and device for realizing audit data storage under multi-version concurrency control |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112162832A true CN112162832A (en) | 2021-01-01 |
| CN112162832B CN112162832B (en) | 2024-02-09 |
Family
ID=73857840
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010932428.5A Active CN112162832B (en) | 2020-09-08 | 2020-09-08 | Method and device for realizing audit data storage under multi-version concurrency control |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112162832B (en) |
Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US5404508A (en) * | 1992-12-03 | 1995-04-04 | Unisys Corporation | Data base backup and recovery system and method |
| WO2005069823A2 (en) * | 2004-01-15 | 2005-08-04 | Jun Song | Centralized transactional security audit for enterprise systems |
| KR20050091470A (en) * | 2004-03-12 | 2005-09-15 | 주식회사 와이드티엔에스 | Transaction analysing system for tandem system |
| US20090196423A1 (en) * | 2008-02-01 | 2009-08-06 | Oracle International Corporation | Methods to defend against tampering of audit records |
| US20100318858A1 (en) * | 2009-06-15 | 2010-12-16 | Verisign, Inc. | Method and system for auditing transaction data from database operations |
| CN103365987A (en) * | 2013-07-05 | 2013-10-23 | 北京人大金仓信息技术股份有限公司 | Clustered database system and data processing method based on shared-disk framework |
| US20170286471A1 (en) * | 2016-03-31 | 2017-10-05 | Mckesson Corporation | Methods and apparatuses for enterprise revision-based auditing of database management systems |
| CN109101368A (en) * | 2018-08-20 | 2018-12-28 | 郑州云海信息技术有限公司 | A kind of data processing method and device |
| CN109325044A (en) * | 2018-09-20 | 2019-02-12 | 快云信息科技有限公司 | A kind of the audit log processing method and relevant apparatus of database |
| CN111191247A (en) * | 2019-12-26 | 2020-05-22 | 深圳昂楷科技有限公司 | Database security audit system |
-
2020
- 2020-09-08 CN CN202010932428.5A patent/CN112162832B/en active Active
Patent Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US5404508A (en) * | 1992-12-03 | 1995-04-04 | Unisys Corporation | Data base backup and recovery system and method |
| WO2005069823A2 (en) * | 2004-01-15 | 2005-08-04 | Jun Song | Centralized transactional security audit for enterprise systems |
| KR20050091470A (en) * | 2004-03-12 | 2005-09-15 | 주식회사 와이드티엔에스 | Transaction analysing system for tandem system |
| US20090196423A1 (en) * | 2008-02-01 | 2009-08-06 | Oracle International Corporation | Methods to defend against tampering of audit records |
| US20100318858A1 (en) * | 2009-06-15 | 2010-12-16 | Verisign, Inc. | Method and system for auditing transaction data from database operations |
| CN103365987A (en) * | 2013-07-05 | 2013-10-23 | 北京人大金仓信息技术股份有限公司 | Clustered database system and data processing method based on shared-disk framework |
| US20170286471A1 (en) * | 2016-03-31 | 2017-10-05 | Mckesson Corporation | Methods and apparatuses for enterprise revision-based auditing of database management systems |
| CN109101368A (en) * | 2018-08-20 | 2018-12-28 | 郑州云海信息技术有限公司 | A kind of data processing method and device |
| CN109325044A (en) * | 2018-09-20 | 2019-02-12 | 快云信息科技有限公司 | A kind of the audit log processing method and relevant apparatus of database |
| CN111191247A (en) * | 2019-12-26 | 2020-05-22 | 深圳昂楷科技有限公司 | Database security audit system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112162832B (en) | 2024-02-09 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| WO2020015190A1 (en) | Method for generating business rule, electronic device, and readable storage medium | |
| CN110009362B (en) | Block chain intelligent contract modification method and device and computer readable storage medium | |
| DE112011100258T5 (en) | Performing aggressive code optimizations with an ability to cancel the changes made by the aggressive optimizations | |
| US10824544B1 (en) | Generating test data as a service for use in testing software during software development | |
| WO2019076102A1 (en) | Data rollback method and system, device, and computer readable storage medium | |
| US20210182054A1 (en) | Preventing unexpected behavior in software systems due to third party artifacts | |
| US8938608B2 (en) | Enabling portions of programs to be executed on system z integrated information processor (zIIP) without requiring programs to be entirely restructured | |
| CN111080390B (en) | Order information modification method, system, equipment and storage medium | |
| EP2802986A1 (en) | Contextual solicitation in a starter application | |
| US8191041B2 (en) | Javascript pre-processing framework | |
| CN112486552A (en) | Server hot update method, device, equipment and storage medium | |
| US8321846B2 (en) | Executable template | |
| CN116909943A (en) | Cache access method and device, storage medium and electronic equipment | |
| CN114253713A (en) | Asynchronous batch processing method and system based on reactivor | |
| CN112162832B (en) | Method and device for realizing audit data storage under multi-version concurrency control | |
| CN109783718B (en) | Repeat request judgment method and device | |
| CN111045789B (en) | Virtual machine starting method and device, electronic equipment and storage medium | |
| US10467076B1 (en) | System and method of input validation | |
| US11366658B1 (en) | Seamless lifecycle stability for extensible software features | |
| CN107632893B (en) | Message queue processing method and device | |
| US11568060B2 (en) | Modular taint analysis with access paths | |
| CN112882994A (en) | Log extraction method and device | |
| US10338903B2 (en) | Simulation-based code duplication | |
| CN111984998A (en) | Mandatory access control method and device for database | |
| CN111859403A (en) | Method and device for determining dependency vulnerability, electronic equipment and storage medium |
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 |