WO2019019706A1 - Data table backup method based on oracle database, and server - Google Patents

Abstract

The present invention is applicable to the technical field of database processing, provides a data table backup method based on an Oracle database, and a server. The method comprises: establishing a backup data table with the same table structure as a target data table, and setting an access right for the backup data table according to the target data table, wherein the target data table is an Excel table; acquiring the type of data in the target data table, wherein the type of data in the target data table comprises data updated in a non-real-time manner and data updated in a real-time manner; and according to the type of data in the target data table, backing up, by means of the backup data table, data to be backed up in the target data table. According to the data table backup method based on an Oracle database, and the server, data backup can be carried out on non-partitioned tables without processing by professional DBA personnel, such that the operational efficiency of data backup can be greatly improved, and the operability can be enhanced.

Description

Data table backup method and server based on Oracle database

This application claims the priority of the Chinese Patent Application entitled "Database Backup Method and Server Based on Oracle Database" filed on July 27, 2017, with the application number of 201710622205.7, the entire contents of which are incorporated by reference. In this application.

Technical field

The application belongs to the technical field of database processing, and particularly relates to a data table backup method and a server based on an Oracle database.

Background technique

Various systems generate a large amount of data during use, such as customer order data, operation log data, attendance performance and other result data. As the amount of data increases, the query speed of the system will become slower and slower during use. The usual practice is to archive historical data and move historical data to a backup table. It is also because the data volume is too large to affect the performance of the system, so the data archiving problem should be considered when designing the table structure in the initial stage. The easiest and most common method is to create a partition table storage for the database, such as partitioning by month. When doing data archiving, move the historical partition directly out of the partition table. Generally, when a partition table is used to store data and the data is archived, the service needs to be interrupted, and the professional DBA personnel (Database Administrator) handles the processing, and the operability is poor and the operation efficiency is low.

technical problem

In view of this, the embodiment of the present application provides a data table backup method and a server based on an Oracle database, so as to solve the problem of poor operability and low operation efficiency of the data table backup of the database in the prior art.

Technical solution

An aspect provided by the application provides a data table backup method based on an Oracle database, including:

Establishing a backup data table with the same table structure as the target data table, and setting access rights for the backup data table according to the target data table; the target data table is an excel table;

Obtaining a type of data in the target data table; the type of data in the target data table includes non-real-time update data and real-time update data;

The data to be backed up in the target data table is backed up by the backup table data table according to the type of data in the target data table.

Beneficial effect

Compared with the prior art, the embodiment of the present application has the beneficial effects that: in the embodiment of the present application, a backup data table having the same table structure as the target data table is first established, and then the backup data table is set according to the target data table. Access rights, and then backing up the data to be backed up in the target data table according to the type of data in the target data table, and can perform data backup on the non-partition table without requiring professional DBA personnel to process, which can greatly improve The efficiency of data backup operations.

DRAWINGS

1 is a flowchart of a data table backup method based on an Oracle database according to Embodiment 1 of the present application;

2 is a flowchart of an implementation of step S103 in FIG. 1;

FIG. 3 is another implementation flowchart of step S103 in FIG. 1;

4 is a further implementation flowchart of step S103 in FIG. 1;

5 is a schematic diagram of a server provided in Embodiment 2 of the present application;

FIG. 6 is a block diagram of a program module according to Embodiment 2 of the present application.

Embodiments of the invention

In the following description, for purposes of illustration and description However, it will be apparent to those skilled in the art that the present invention may be practiced in other embodiments without these specific details. In other instances, detailed descriptions of well-known systems, devices, circuits, and methods are omitted so as not to obscure the description of the application.

In order to explain the technical solutions described in the present application, the following description will be made by way of specific embodiments.

Embodiment 1

FIG. 1 is a flowchart showing an implementation process of an Oracle database-based data table backup method according to Embodiment 1 of the present application, which is described in detail as follows:

Step S101, establishing a backup data table having the same table structure as the target data table, and setting access rights for the backup data table according to the target data table.

The target data table is a data table that needs to be backed up, and may be an excel table, for example, a data table based on an Oracle database. The table structure of the target data table can be a table structure in the form of excel, and corresponding code information is included to implement the corresponding functions. In addition, according to the division of functions, the code structure of the table structure of the data table of different functions is also different.

In addition, the table structure of the target data table may also contain information such as numbers and fields. Specifically, each table structure may include a number, which is a unique identifier of the corresponding table structure; each table structure contains a field that has a certain relevance according to design requirements.

In this step, the setting the access permission for the backup data table according to the target data table is specifically: combining the access rights of the target data table, and setting a certain user and a certain set of the created backup data table according to actual needs. The access rights of some users. For example, if the target data table only allows access by a specific user, the backup data table can be set and only specific users can be accessed to prevent data leakage.

Step S102: Acquire a type of data in the target data table.

The type of data in the target data table may include non-real time update data and real time update data. Among them, non-real-time update data refers to data that is not updated or changed in real time, such as attendance data, performance data, and various summary data. Since the non-real-time update data is not updated in real time, it is only calculated by a specific time, for example, it is generated every night or at the end of each month. Therefore, for non-real-time update data, only non-calculated time is required for archiving, and no need to consider the business. influences. Real-time update data refers to data that is updated or changed in real time, such as the operation log and some synchronization intermediate table data (update synchronization status field after synchronization is completed).

Specifically, the type of the data in the target data table may be identified by the data type identifier, and each data type identifier may correspond to multiple pieces of data. Typically, the data stored in a data table is a data type.

In an embodiment, the acquiring the type of the data in the target data table may specifically include:

Presetting the data type identifier corresponding to the non-real time update data and the real time update data;

Determining to be non-real-time update data or real-time update data according to the data type identifier in the target data table.

The determining, according to the data type identifier in the target data table, the non-real-time update data or the real-time update data may be:

Determining whether the data is non-real-time update data or real-time update data according to the data type identifier of each piece of data; or

The data in the data table is determined to be non-real-time update data or real-time update data according to the data type identifier corresponding to each data table.

Step S103: Back up data to be backed up in the target data table by using the backup table data table according to the type of data in the target data table.

In this step, different processes are required for non-real-time update data and real-time update data to back up the data to be backed up in the target data table.

Referring to FIG. 2, when the data in the target data table is non-real-time update data, step S103 can be specifically implemented by the following process:

Step S201, the data to be backed up in the target data table is transferred to the backup data table.

The transferring the data to be backed up in the target data table to the backup data table is specifically: transferring the data to be backed up in the target data table to the backup data in batches according to time or a primary key In the table. For example, if the historical data of the target data table for more than 3 months is to be archived, the data within 3 months of the target data table may be inserted into the backup data table in batches by time or primary key.

Step S202, establishing a primary key and an index for the backup data table according to the target data table.

The primary key is the unique index of the data table. For example, the student table has a student number and a name. The name may have a duplicate name, but the student number is unique. Search for a record from the student list, such as finding a person. , you can only find it according to the student number, in order to find the only one. For example, a computer manufacturer's database stores product information of the whole machine and accessories, and a table for storing product information of the whole machine is called a Pc table (reference table), and a table for storing the supply information of the parts is called a Parts table ( Refer to the table). To set a foreign key, in the reference table (referencing The table, that is, the Pc table) and the referenced table (the parts table), the corresponding two fields must be indexed.

In this step, after the data to be backed up in the target data table is transferred to the backup data table, a primary key and an index need to be established on the backup data table according to the primary key and the index in the target data table, so that The data in the backup data table can be normally referenced according to the data relationship in the target data table.

Step S203, changing the table name of the backup data table after the primary key and the index is established to the table name of the target data table.

The data to be backed up in the target data table is transferred to the backup data table, and after the primary key and the index are established for the backup data table according to the target data table, except for the table name of the data table, The backup data table has been identical to the table structure and data information of the target data table. At this time, changing the table name of the backup key data table after the primary key and the index is changed to the table name of the target data table, the process of backing up the target data table can be completed.

Taking the target data table as the attendance data table as an example, it is assumed that the historical data of the attendance data table for more than 3 months should be archived, and the implementation process is as follows:

Create a backup data table (table name B) with the same table structure as the attendance data table (table name A), and refer to the attendance data table A to authorize the backup data table B, so as to limit the access of certain users to the backup. Data table B, querying the data in the backup data table B;

The data within 3 months of the attendance data sheet A is inserted into the backup data table B in batches by time or primary key. Since the attendance data table A is a non-real-time update data table, it can be directly inserted into the batch through the time or the primary key. Back up data table B without regard to chronological issues;

The primary key, the index, and the like are established on the backup data table B by referring to the attendance data table A table, so that the data in the backup data table B can be correctly referenced;

The table name of the attendance data table A is renamed to the data table C, and the table name of the backup data table B is renamed to the table A, that is, the process of backing up the data in the attendance data table A can be completed.

Referring to FIG. 3, when the data in the target data table is real-time update data, step S103 can be specifically implemented by the following process:

Step S301, establishing a primary key and an index for the backup data table according to the target data table.

In this step, after the data to be backed up in the target data table is transferred to the backup data table, a primary key and an index need to be established on the backup data table according to the primary key and the index in the target data table, so that The data in the backup data table can be normally referenced according to the data relationship in the target data table. For details, refer to related content in step S202, and details are not described herein again.

Step S302, the table name of the target data table is changed, and the table name of the backup data table after the primary key and the index is established is changed to the table name before the target data table is changed.

Among them, the table name can be changed by a new table name. For example, if the table name of the target data table is Table A and the table name of the backup data table is Table B, the table name of the target data table may be changed to Table C, and then the table name of the backup data table will be Change to Table A.

In step S303, the data in the target data table after the table name is changed is transferred to the renamed backup data table in the order of the recording time from the back to the front.

The step S303 may specifically be: transferring the data to be backed up in the target data table to the backup data table in batches according to time or a primary key. For example, if the historical data of the target data table for more than 3 months is to be archived, the data within 3 months of the target data table may be inserted into the backup data table in batches by time or primary key.

If the data table only has an insert operation, such as an operation log, this step does not need to interrupt the service, and the impact on the service is almost negligible within 1 second. If the data table has an insert update operation, such as some synchronization intermediate table data (the synchronization status field is updated after the synchronization is completed), the migration data should preferentially migrate the new data in step S303, avoiding an error when the program is updated, and affecting the business. In a few seconds or so, after the data is archived, only a little comparison of the data can be done to completely eliminate the impact.

Optionally, after step S303, the method further includes: performing data comparison processing according to the data in the target data table and the data in the backup data table to prevent an error when the program is updated.

Taking the target data table as an operation log as an example, it is assumed that the historical data of the operation log data table for more than three months is to be archived, and the implementation process is as follows:

Create a backup data table (table name B) with the same table structure as the operation log data table (table name A), and authorize the backup data table B with reference to the operation log data table A, so as to define a certain portion of users. Access the backup data table B to query the data in the backup data table B;

The primary key, the index, and the like are established on the backup data table B with reference to the operation log data table A, so that the data in the backup data table B can be correctly referenced;

Rename the table name of the operation log data table A to the data table C, and rename the table name of the backup data table B to the table A;

The data within 3 months of the operation log data table C is inserted into the backup data table A in batches according to the time or the primary key in the order from the back to the front of the recording time.

Further, when the data in the target data table is real-time update data, the backup data table having the same table structure as the target data table is specifically configured to: establish a time-based partition with the same table structure as the target data table. And backing up the data table, where the backup data table includes a first partition, and the start time corresponding to the first partition is a current time. For example, the backup data table is partitioned by time, including the partition P1, the partition P2, the partition P3, and the like, wherein the time starting point corresponding to the partition P1 is earlier than the current time, and the partition P2, the partition P3, and the like may be partitioned by month. For example, if the current time is May 15th, the time starting point corresponding to the partition P1 may be a certain day of May, for example, May 14.

The step S103 can be specifically implemented by the following process:

Step S401, establishing a primary key and an index for the backup data table according to the target data table.

In this step, after the data to be backed up in the target data table is transferred to the backup data table, a primary key and an index need to be established on the backup data table according to the primary key and the index in the target data table, so that The data in the backup data table can be normally referenced according to the data relationship in the target data table. For details, refer to related content in step S202, and details are not described herein again.

Step S402, the table name of the target data table is changed, and the table name of the backup data table after the primary key and the index is established is changed to the table name before the target data table is changed.

Among them, the table name can be changed by a new table name. For example, if the table name of the target data table is Table A and the table name of the backup data table is Table B, the table name of the target data table may be changed to Table C, and then the table name of the backup data table will be Change to Table A.

Step S403, the target data table after the table name is changed is exchanged with the first partition, and the first partition is moved out of the backup data table after the table name is changed after the preset time.

Wherein, the exchange between the target data table after the table name change and the first partition can be implemented by using an sql operation, for example, sql: ALTER TABLE A EXCHANGE PATITION P1 WITH TABLE C, that is, the partition P1 is exchanged with the data of the target data table C. After the preset time for data exchange is completed, the first partition can be moved out of the backup data table.

For example, the historical data of more than three months in the target data table is archived, and almost every data in three months may be modified in real time. The implementation process is as follows:

Create a time-based partitioned backup data table (table name B) with the same table structure as the target data table (table name A). The partition of the backup data table B includes partition P1, partition P2, partition P3, etc., where The starting point time corresponding to the partition P1 is earlier than the current time;

The primary key, the index, and the like are established on the backup data table B with reference to the target data table A table, so that the data in the backup data table B can be correctly referenced;

Rename the table name of the target data table A to the data table C, and rename the table name of the backup data table B to the table A;

Exchange data table C with the P1 partition of data table A, the specific process is sql: ALTER TABLE A EXCHANGE PATITION P1 WITH TABLE C;

After completing the data exchange for 3 months, the partition P1 is moved out of the data table A.

The above data table backup method based on the Oracle database first establishes a backup data table with the same table structure as the target data table, and then sets access rights for the backup data table according to the target data table, and then according to the target data table. The type of the data is used to back up the data to be backed up in the target data table, and the data backup of the non-partition table can be performed without the need of professional DBA personnel to process, which can greatly improve the operation efficiency of the data backup.

It should be understood that the size of the sequence of the steps in the above embodiments does not mean that the order of execution is performed. The order of execution of each process should be determined by its function and internal logic, and should not be construed as limiting the implementation process of the embodiments of the present application.

Embodiment 2

Corresponding to the picture matching method described in the foregoing embodiment, FIG. 5 is a schematic diagram showing an operating environment of the picture matching program provided by the embodiment of the present application. For the convenience of explanation, only the parts related to the present embodiment are shown.

In the present embodiment, the computer readable instructions 500 are installed and run in the server 50. The server 50 can include, but is not limited to, a memory 501 and a processor 502. FIG. 5 shows only server 50 with components 501-522, but it should be understood that not all illustrated components may be implemented, and more or fewer components may be implemented instead.

The memory 501 may be an internal storage unit of the server 50, such as a hard disk or memory of the server 50, in some embodiments. The memory 501 may also be an external storage device of the server 50 in other embodiments, such as a plug-in hard disk equipped on the server 50, a smart memory card (SMC), and a secure digital (Secure) Digital, SD) cards, flash cards, etc. Further, the memory 501 may also include both an internal storage unit of the server 50 and an external storage device. The memory 501 is configured to store application software and various types of data installed in the server 50, such as program code of a data table backup program based on an Oracle database. The memory 501 can also be used to temporarily store data that has been output or is about to be output.

The processor 502 can be a central processor (Central) in some embodiments A processing unit (CPU), a microprocessor or other data processing chip for running program code or processing data stored in the memory 501, for example, executing the Oracle database-based data table backup program.

The components 501-522 of the server 50 communicate with one another via a system bus.

Please refer to FIG. 6 , which is a functional block diagram of computer readable instructions 500 provided by an embodiment of the present application. In this embodiment, the computer readable instructions 500 may be partitioned into one or more modules, the one or more modules being stored in the memory 501 and being processed by one or more processors (this Embodiments are performed by the processor 502) to complete the application. For example, in FIG. 6, the picture matching program 500 can be divided into a data table establishing module 601, a data type obtaining module 602, and a backup module 603. A module, as referred to herein, refers to a series of computer readable instruction instructions that are capable of performing a particular function, and are more suitable than the program for describing the execution of the computer readable instructions 500 in the server 50. The following description will specifically describe the functions of the modules 601-603.

The data table establishing module 601 is configured to establish a backup data table with the same table structure as the target data table, and set access rights for the backup data table according to the target data table. The target data table is an excel table.

The data type obtaining module 602 is configured to acquire a type of data in the target data table. The type of data in the target data table includes non-real time update data and real time update data.

The backup module 603 is configured to back up data to be backed up in the target data table by using the backup table data table according to the type of data in the target data table.

Optionally, when the data in the target data table is non-real time update data, the backup module 603 may be divided into a first data transfer unit, a first setup unit, and a first rename unit.

a first data transfer unit, configured to transfer data to be backed up in the target data table to the backup data table;

a first establishing unit, configured to establish a primary key and an index for the backup data table according to the target data table;

The first renaming unit is configured to change the table name of the backup data table after the primary key and the index is established to the table name of the target data table.

Optionally, when the data in the target data table is real-time update data, the backup module 603 may be divided into a second establishing unit, a second rename unit, and a second data transfer unit.

And a second establishing unit, configured to establish a primary key and an index for the backup data table according to the target data table.

a second renaming unit, configured to change a table name of the target data table, and change a table name of the backup data table after the primary key and the index is established to a table name before the target data table is changed.

The second data transfer unit is configured to transfer the data in the target data table after the table name is changed to the backup data table after the rename according to the recording time from the back to the front.

Optionally, the first data transfer unit or the second data transfer unit is specifically configured to batch transfer the data to be backed up in the target data table to the backup data table according to a time or a primary key.

Optionally, when the data in the target data table is real-time update data, the backup data table that is the same as the table structure of the target data table is specifically configured to: establish the same time-based partitioning with the table structure of the target data table. The backup data table includes a first partition, and the start time corresponding to the first partition is a current time. The backup module 603 can be divided into a third establishing unit, a third rename unit, and a third backup unit.

And a third establishing unit, configured to establish a primary key and an index for the backup data table according to the target data table.

The third renaming unit changes the table name of the target data table, and changes the table name of the backup data table after the primary key and the index is established to the table name before the target data table is changed.

The third backup unit exchanges the target data table after the table name change with the first partition, and moves the first partition out of the backup data table after the table name is changed after the preset time.

It will be clearly understood by those skilled in the art that, for convenience and brevity of description, only the division of each functional unit and module described above is exemplified. In practical applications, the above functions may be assigned to different functional units according to needs. The module is completed by dividing the internal structure of the device into different functional units or modules to perform all or part of the functions described above. Each functional unit and module in the embodiment may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit, and the integrated unit may be implemented by hardware. Formal implementation can also be implemented in the form of software functional units. In addition, the specific names of the respective functional units and modules are only for the purpose of facilitating mutual differentiation, and are not intended to limit the scope of protection of the present application. For the specific working process of the unit and the module in the foregoing system, reference may be made to the corresponding process in the foregoing method embodiment, and details are not described herein again.

In the above embodiments, the descriptions of the various embodiments are different, and the parts that are not detailed or described in the specific embodiments may be referred to the related descriptions of other embodiments.

Those of ordinary skill in the art will appreciate that the elements and algorithm steps of the various examples described in connection with the embodiments disclosed herein can be implemented in electronic hardware or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the solution. A person skilled in the art can use different methods to implement the described functions for each particular application, but such implementation should not be considered to be beyond the scope of the present application.

The above-mentioned embodiments are only used to explain the technical solutions of the present application, and are not limited thereto; although the present application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that they can still implement the foregoing embodiments. The technical solutions described in the examples are modified or equivalently replaced with some of the technical features; and the modifications or substitutions do not deviate from the spirit and scope of the technical solutions of the embodiments of the present application, and should be included in Within the scope of protection of this application.

Claims (20)

1. A data table backup method based on an Oracle database, characterized in that:

   Establishing a backup data table with the same table structure as the target data table, and setting access rights to the backup data table according to the target data table; the target data table is an excel table;

   Obtaining a type of data in the target data table; the type of data in the target data table includes non-real-time update data and real-time update data;

   The data to be backed up in the target data table is backed up by the backup table data table according to the type of data in the target data table.
2. The method for backing up an Oracle database-based data table according to claim 1, wherein when the data in the target data table is non-real-time update data, the data is passed according to the type of the data in the target data table. The backup table data table backs up the data to be backed up in the target data table, including:

   Transferring the data to be backed up in the target data table to the backup data table;

   Establishing a primary key and an index for the backup data table according to the target data table;

   Change the table name of the backup data table after the primary key and index is established to the table name of the target data table.
3. The method for backing up an Oracle database-based data table according to claim 2, wherein the transferring the data to be backed up in the target data table to the backup data table is specifically:

   The data to be backed up in the target data table is batch-transferred to the backup data table according to time or primary key.
4. The method for backing up an Oracle database-based data table according to claim 1, wherein when the data in the target data table is real-time update data, according to the type of data in the target data table, The backup table data table backs up the data to be backed up in the target data table, including:

   Establishing a primary key and an index for the backup data table according to the target data table;

   Changing the table name of the target data table, and changing the table name of the backup data table after the primary key and the index is established to the table name before the target data table is changed;

   The data in the target data table after the table name is changed is transferred to the renamed backup data table in the order of the recording time from the back to the front.
5. The data table backup method based on the Oracle database of claim 4, wherein when the data in the target data table is real-time update data, the backup data table having the same table structure as the target data table is specifically configured. a backup data table that is partitioned by time according to the same table structure of the target data table, the backup data table includes a first partition, and a start time corresponding to the first partition is a current time;

   The backing up the data to be backed up in the target data table by using the backup table data table according to the type of the data in the target data table includes:

   Establishing a primary key and an index for the backup data table according to the target data table;

   Changing the table name of the target data table, and changing the table name of the backup data table after the primary key and the index is established to the table name before the target data table is changed;

   The target data table after the table name is changed is exchanged with the first partition, and the first partition is moved out of the backup data table after the table name is changed after the preset time.
6. A server, comprising:

   The data table establishing module is configured to establish a backup data table with the same table structure as the target data table, and set access rights for the backup data table according to the target data table. Wherein, the target data table is an excel table;

   a data type obtaining module, configured to acquire a type of data in the target data table. The type of data in the target data table includes non-real time update data and real time update data;

   And a backup module, configured to back up data to be backed up in the target data table by using the backup table data table according to a type of data in the target data table.
7. The server according to claim 6, wherein when the data in the target data table is non-real time update data, the backup module comprises:

   a first data transfer unit, configured to transfer data to be backed up in the target data table to the backup data table;

   a first establishing unit, configured to establish a primary key and an index for the backup data table according to the target data table;

   The first renaming unit is configured to change the table name of the backup data table after the primary key and the index is established to the table name of the target data table.
8. The server according to claim 7, wherein the first data transfer unit or the second data transfer unit is specifically configured to: batch transfer the data to be backed up in the target data table to the batch according to time or primary key In the backup data table.
9. The server according to claim 6, wherein when the data in the target data table is real-time update data, the backup module comprises:

   a second establishing unit, configured to establish a primary key and an index for the backup data table according to the target data table;

   a second renaming unit, configured to change a table name of the target data table, and change a table name of the backup data table after the primary key and the index is established to a table name before the target data table is changed;

   The second data transfer unit is configured to transfer the data in the target data table after the table name is changed to the backup data table after the rename according to the recording time from the back to the front.
10. The server according to claim 9, wherein when the data in the target data table is real-time update data, the backup data table having the same table structure as the target data table is specifically: establishing and target data table. The backup table includes the first partition, and the start time corresponding to the first partition is the current time; the backup module includes:

    a third establishing unit, configured to establish a primary key and an index for the backup data table according to the target data table;

    a third renaming unit, changing a table name of the target data table, and changing a table name of the backup data table after the primary key and the index is established to a table name before the target data table is changed;

    The third backup unit exchanges the target data table after the table name change with the first partition, and moves the first partition out of the backup data table after the table name is changed after the preset time.
11. A server comprising a memory, a processor, and computer readable instructions stored in the memory and operative on the processor, wherein the processor implements the following steps when the computer readable instructions are executed :

    Establishing a backup data table with the same table structure as the target data table, and setting access rights to the backup data table according to the target data table; the target data table is an excel table;

    Obtaining a type of data in the target data table; the type of data in the target data table includes non-real-time update data and real-time update data;

    The data to be backed up in the target data table is backed up by the backup table data table according to the type of data in the target data table.
12. The server according to claim 11, wherein when the data in the target data table is non-real time update data, the backup table is used according to the type of data in the target data table. The data table backs up the data to be backed up in the target data table, including:

    Transferring the data to be backed up in the target data table to the backup data table;

    Establishing a primary key and an index for the backup data table according to the target data table;

    Change the table name of the backup data table after the primary key and index is established to the table name of the target data table.
13. The server according to claim 12, wherein the transferring the data to be backed up in the target data table to the backup data table is specifically:

    The data to be backed up in the target data table is batch-transferred to the backup data table according to time or primary key.
14. The server according to claim 11, wherein when the data in the target data table is real-time update data, according to the type of data in the target data table, the data is The backup of the data to be backed up in the target data table includes:

    Establishing a primary key and an index for the backup data table according to the target data table;

    Changing the table name of the target data table, and changing the table name of the backup data table after the primary key and the index is established to the table name before the target data table is changed;

    The data in the target data table after the table name is changed is transferred to the renamed backup data table in the order of the recording time from the back to the front.
15. The server according to claim 14, wherein when the data in the target data table is real-time update data, the backup data table having the same table structure as the target data table is specifically: establishing and target data table. The table structure is the same as the backup data table partitioned by time, the backup data table includes a first partition, and the start time corresponding to the first partition is the current time;

    The backing up the data to be backed up in the target data table by using the backup table data table according to the type of the data in the target data table includes:

    Establishing a primary key and an index for the backup data table according to the target data table;

    Changing the table name of the target data table, and changing the table name of the backup data table after the primary key and the index is established to the table name before the target data table is changed;

    The target data table after the table name is changed is exchanged with the first partition, and the first partition is moved out of the backup data table after the table name is changed after the preset time.
16. A computer readable storage medium storing computer readable instructions, wherein the computer readable instructions, when executed by a processor, implement the following steps:

    Establishing a backup data table with the same table structure as the target data table, and setting access rights to the backup data table according to the target data table; the target data table is an excel table;

    Obtaining a type of data in the target data table; the type of data in the target data table includes non-real-time update data and real-time update data;

    The data to be backed up in the target data table is backed up by the backup table data table according to the type of data in the target data table.
17. The computer readable storage medium according to claim 16, wherein when the data in the target data table is non-real time update data, the backup table is used according to the type of data in the target data table. The data table backs up the data to be backed up in the target data table, including:

    Transferring the data to be backed up in the target data table to the backup data table;

    Establishing a primary key and an index for the backup data table according to the target data table;

    Change the table name of the backup data table after the primary key and index is established to the table name of the target data table.
18. The computer readable storage medium according to claim 17, wherein the transferring the data to be backed up in the target data table to the backup data table is specifically:

    The data to be backed up in the target data table is batch-transferred to the backup data table according to time or primary key.
19. The computer readable storage medium according to claim 16, wherein when the data in the target data table is real-time update data, the data is passed through the backup table according to a type of data in the target data table. The table backs up the data to be backed up in the target data table, including:

    Establishing a primary key and an index for the backup data table according to the target data table;

    Changing the table name of the target data table, and changing the table name of the backup data table after the primary key and the index is established to the table name before the target data table is changed;

    The data in the target data table after the table name is changed is transferred to the renamed backup data table in the order of the recording time from the back to the front.
20. The computer readable storage medium according to claim 19, wherein when the data in the target data table is real-time update data, the establishing a backup data table having the same table structure as the target data table is specifically: establishing a backup data table partitioned by time according to a table structure of the target data table, where the backup data table includes a first partition, and a start time corresponding to the first partition is a current time;

    The backing up the data to be backed up in the target data table by using the backup table data table according to the type of the data in the target data table includes:

    Establishing a primary key and an index for the backup data table according to the target data table;

    Changing the table name of the target data table, and changing the table name of the backup data table after the primary key and the index is established to the table name before the target data table is changed;

    The target data table after the table name is changed is exchanged with the first partition, and the first partition is moved out of the backup data table after the table name is changed after the preset time.