CN108090095B - Method and device for reconstructing database in batches - Google Patents

Abstract

The invention discloses a method and a device for batch rebuilding a database. Wherein, the method includes: acquiring database information on one or more servers deployed in a distributed manner, wherein the database information at least includes: the name of the database, the size of the file stored in the database, and the total number of rows of the data table stored in the database; Determine the database that needs to be rebuilt according to the size of the file stored in the database and/or the total number of rows in the table; rebuild the database that needs to be rebuilt. The invention solves the technical problem that the prior art cannot realize the batch reconstruction of databases on multiple servers deployed in a distributed manner.

Description

Method and device for batch rebuilding database

technical field

The present invention relates to the technical field of computer networks, in particular, to a method and apparatus for batch rebuilding a database.

Background technique

In this field, the emergence of database technology has achieved the purpose of unified analysis, management and sharing of large amounts of computer data in modern information science systems. However, in the process of storing computer data in a database (for example, a SQL-server database), it is usually difficult to store the data that needs to be analyzed in multiple dimensions in one step. In order to realize the data storage in the database, the solution usually adopted is to add a processing link, first store the original data obtained by the computer into a process database (for example: receiver database), and then further process the data stored in the process database, thereby Generate the final database (eg DataWarehouse database) that meets the profiling conditions. In this process, with the continuous accumulation of process data, the data stored in the process database will continue to increase, especially the storage of many intermediate process databases-receiver databases will undoubtedly cause huge pressure on the hard disk of the server.

In order to avoid the continuous increase of the data stored in the above-mentioned process database, it is necessary to periodically use a template database to rebuild such a process database. Because the template database only contains information such as the correct table structure of the database, without any data, the amount of data and the occupied disk space are relatively small. The solution adopted in the prior art is to obtain the size of the database file stored in the database by checking the file size of the local disk of the server, so as to determine whether the database needs to be rebuilt according to the size of the database file. For a distributed database, since multiple distributed servers are used to store the database in a distributed manner, it is difficult to ensure that the storage paths of the database files stored in the database are consistent. The database is reconstructed, or the database on a single server is reconstructed by using a script program, etc., and multiple databases on all servers deployed in a distributed manner cannot be reconstructed in batches.

Aiming at the problem that the above-mentioned prior art cannot realize batch reconstruction of databases on multiple servers deployed in a distributed manner, no effective solution has been proposed yet.

SUMMARY OF THE INVENTION

Embodiments of the present invention provide a method and apparatus for batch rebuilding a database, so as to at least solve the technical problem that the prior art cannot implement batch rebuilding of databases on multiple servers deployed in a distributed manner.

According to an aspect of the embodiments of the present invention, there is provided a method for rebuilding a database in batches, including: acquiring database information on one or more servers deployed in a distributed manner, wherein the database information at least includes: the name of the database, the data stored in the database The size of the file and the total number of rows of the data table stored in the database; determine the database to be rebuilt according to the size of the file stored in the database and/or the total number of rows of the table; rebuild the database to be rebuilt.

Further, acquiring database information on one or more servers deployed in a distributed manner includes: calling a database system table on the server through a database management system; and acquiring database information from the database system table.

Further, after acquiring database information on one or more servers deployed in a distributed manner, the above method further includes: acquiring identification information on one or more servers deployed in a distributed manner; storing the identification information and the database information on the servers in a database temporary table.

Further, determining the database to be rebuilt according to the size of the file stored in the database and/or the total number of rows in the data table includes: judging whether the database satisfies a preset condition, wherein the preset condition includes any one of the following: the file stored in the database The size of the database is greater than the preset threshold, and the total number of rows of the table stored in the database is greater than the preset number of rows; the database that meets the preset condition is filtered from the database temporary table.

Further, rebuilding the database that needs to be rebuilt includes: obtaining the database that needs to be rebuilt in the temporary table of the database; deleting the database that needs to be rebuilt; and using the template database to rebuild the database that needs to be rebuilt.

Further, before deleting the database that needs to be rebuilt, the method includes: backing up the database that needs to be rebuilt to a local disk or a backup server.

Further, after using the template database to rebuild the database to be rebuilt, the method further includes: verifying the rebuilt database; and deleting the database backed up in the local disk or the backup server when the verification is successful.

According to another aspect of the embodiments of the present invention, an apparatus for rebuilding databases in batches is further provided, including: a first obtaining module configured to obtain database information on one or more servers deployed in a distributed manner, wherein the database information is at least Including: the name of the database, the size of the file stored in the database, the total number of rows of the data table stored in the database; the determining module is used to determine the database to be rebuilt according to the size of the file stored in the database and/or the total number of rows of the data table ; Create a module for rebuilding the database that needs to be rebuilt.

Further, the above-mentioned first obtaining module includes: a calling module for calling the database system table on the server through the database management system; and a second obtaining module for obtaining database information from the database system table.

Further, the above-mentioned device also includes: a third acquisition module for acquiring the identification information of one or more servers deployed in a distributed manner; a first storage module for storing the identification information and database information on the server in a temporary database table middle.

Further, the above-mentioned determination module further includes: judging whether the database satisfies a preset condition, wherein the preset condition includes at least any one of the following: the size of the file stored in the database is greater than the preset threshold, and the total number of rows of the table stored in the database is greater than The preset number of rows; the database that meets the preset conditions is filtered from the database temporary table.

Further, the above-mentioned creation module also includes: a fourth acquisition module, for acquiring the database that needs to be rebuilt in the temporary table of the database; the first deletion module, for deleting the database that needs to be rebuilt; The database is rebuilt.

Further, the above-mentioned apparatus further includes: a second storage module for backing up the database that needs to be rebuilt to a local disk or a backup server.

Further, the above device further includes: a verification module for verifying the reconstructed database; a second deletion module for deleting the database backed up in the local disk or the backup server when the verification is successful.

In this embodiment of the present invention, by acquiring database information on one or more servers deployed in a distributed manner, the database information at least includes: the name of the database, the size of the file stored in the database, and the total row of the data table stored in the database. determine the database to be rebuilt according to the size of the files stored in the database and/or the total number of rows in the table; rebuild the database that needs to be rebuilt to achieve batch processing of databases on one or more servers deployed in a distributed manner The purpose is to achieve the technical effect of batch reconstruction of databases on different servers, thereby solving the technical problem that the prior art cannot achieve batch reconstruction of databases on multiple servers deployed in a distributed manner.

Description of drawings

The accompanying drawings described herein are used to provide a further understanding of the present invention and constitute a part of the present application. The exemplary embodiments of the present invention and their descriptions are used to explain the present invention and do not constitute an improper limitation of the present invention. In the attached image:

1 is a flowchart of a method for batch rebuilding a database according to an embodiment of the present invention;

2 is a flowchart of an optional method for batch rebuilding a database according to an embodiment of the present invention;

3 is a flowchart of an optional method for batch rebuilding a database according to an embodiment of the present invention;

4 is a flowchart of an optional method for batch rebuilding a database according to an embodiment of the present invention;

5 is a flowchart of an optional method for batch rebuilding a database according to an embodiment of the present invention;

6 is a flowchart of an optional method for batch rebuilding a database according to an embodiment of the present invention;

7 is a flowchart of a preferred method for batch rebuilding a database in SQL Server according to an embodiment of the present invention; and

FIG. 8 is a schematic diagram of an apparatus for batch rebuilding a database according to an embodiment of the present invention.

Detailed ways

In order to make those skilled in the art better understand the solutions of the present invention, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present invention. Obviously, the described embodiments are only Embodiments are part of the present invention, but not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by persons of ordinary skill in the art without creative efforts shall fall within the protection scope of the present invention.

It should be noted that the terms "first", "second" and the like in the description and claims of the present invention and the above drawings are used to distinguish similar objects, and are not necessarily used to describe a specific sequence or sequence. It is to be understood that the data so used may be interchanged under appropriate circumstances such that the embodiments of the invention described herein can be practiced in sequences other than those illustrated or described herein. Furthermore, the terms "comprising" and "having" and any variations thereof, are intended to cover non-exclusive inclusion, for example, a process, method, system, product or device comprising a series of steps or units is not necessarily limited to those expressly listed Rather, those steps or units may include other steps or units not expressly listed or inherent to these processes, methods, products or devices.

Example 1

According to an embodiment of the present invention, an embodiment of a method for batch rebuilding a database is provided. It should be noted that the steps shown in the flowchart of the accompanying drawings may be executed in a computer system such as a set of computer-executable instructions, and, Although a logical order is shown in the flowcharts, in some cases steps shown or described may be performed in an order different from that herein.

FIG. 1 is a flowchart of a method for batch rebuilding a database according to an embodiment of the present invention. As shown in FIG. 1 , the method includes the following steps:

Step S102: Obtain database information on one or more servers deployed in a distributed manner, where the database information at least includes: the name of the database, the size of the file stored in the database, and the total number of rows of the data table stored in the database.

Specifically, in the above steps, the above server may be a database server for storing and managing data in the database; one or more distributed servers connected to the same domain through the Internet can provide distributed Data storage and management service; the database is composed of multiple data tables, and the data table is the essence of the database; before rebuilding the database on one or more servers deployed in a distributed manner, first obtain the database name on these servers , the size of the file stored in the database, the data table information stored in the database (for example, the total number of rows in the data table), etc.

In an optional embodiment, the above-mentioned database may be a process database in the data storage process of the database.

Step S104: Determine the database to be rebuilt according to the size of the file stored in the database and/or the total number of rows in the table.

Specifically, in the above-mentioned steps, the above-mentioned file may be a file stored in a database, for example, data stored in a database; the size of the above-mentioned file may be the size of the disk space occupied by the file stored in the database, which can be used to represent the storage in the database. The above data table can be a plurality of tables storing data in the database, after obtaining the database information on one or more servers of distributed deployment, according to the file size stored in the database and/or the number of stored data in the database The total number of rows in each table to determine the database that needs to be rebuilt.

It should be noted here that the large amount of data stored in the database will affect the access efficiency of the database, and the number of rows in the table in the database will also affect the response speed of the database. Therefore, the present invention adopts the file size and table stored in the database. There are two indicators of the total number of rows to determine the database that needs to be rebuilt, and rebuild the database that needs to be rebuilt, thereby improving data access efficiency and response speed.

In a preferred embodiment, the database is reconstructed only when the size of the file stored in the database and the total number of rows of the table satisfy a certain condition, thereby improving the accuracy.

Step S106, rebuild the database that needs to be rebuilt.

Specifically, in the above steps, after the database to be rebuilt is determined according to the file size stored in the database and the total number of rows of multiple tables stored in the database, the determined database to be rebuilt is rebuilt based on template data.

It should be noted here that in order to avoid the continuous increase of data accumulated in the process database in the process of storing data for a long time in the database, it not only occupies disk space, but also affects the access speed of the database. To rebuild, the process of rebuilding is to first store the data of the table in the database in the backup space, delete the original table and index, rebuild the empty table and index, import the data into the new table or index, and rebuild the database through the database. , which can clear the old data, thereby reducing the space occupied by the disk and improving the access speed of the database.

It can be seen from the above that in the above-mentioned embodiment of the present application, by obtaining the file size and the number of rows of the table stored in the databases on different servers in the same domain, and according to the two indicators of the size of the file and the number of rows of the table stored in the database to determine the database that needs to be rebuilt, and finally rebuild the database that needs to be rebuilt based on the template data. It is easy to note that the solutions disclosed in the above-mentioned embodiments of the present application do not use the current disk to obtain the file size of the database occupied disk space, but obtain the database information on multiple different servers from the database management system. The size and the number of rows in the table are analyzed to determine the database that needs to be rebuilt, which achieves the purpose of batch processing the databases on one or more servers deployed in a distributed manner, thereby realizing the batch reconstruction of databases on different servers. The technical effect further solves the technical problem that the existing technology cannot realize the batch reconstruction of the databases on multiple servers deployed in a distributed manner.

As an optional embodiment, as shown in FIG. 2 , in the foregoing step S102, obtaining database information on one or more servers deployed in a distributed manner may include the following steps:

Step S202, calling the database system table on the server through the database management system;

Step S204, acquiring database information from the database system table.

Specifically, in the above steps, the above-mentioned database management system may be used for large-scale software for manipulating and managing the databases on one or more servers deployed in the above-mentioned distribution. In an optional embodiment, the database management system may be SQL Server relational database management system, the above-mentioned database system table can be the data system table on different servers of the above-mentioned distributed deployment, and stores the information of all the databases stored on the server, for example, various types of data created by the user in the database Table information, file size stored in the database, etc. Based on the above steps S202 to S204, the database management system (for example, SQL Server) in the distributed database is used to call the database system tables on one or more servers deployed in a distributed manner, according to the database information recorded in the database system tables on different servers , you can obtain database information on each server.

In an optional embodiment, the above-mentioned database can be a SQL Sever database, and the above-mentioned database system table can be a system table in the SQL Sever database, such as Sysdatabases, Sysxlogins, Systypes, Sysusers, and Sysobjects, wherein the system table Sysdatabases exists in SQL Sever. In Sever's Master database, it is used to store all the databases of the current system, the system table Sysxlogins is used to store all accounts that can log in to SQL Sever; the system table Systypes, which exists in each database, is used to store the default users in the system Types and user-defined user types, the system table Sysusers is used to store users and roles in each database, and the system table Sysobjects is used to store each object (constraint, default, log, rule, stored procedure) created in the database ).

It should be noted here that the existing technology obtains the file size stored in the SQL Server database by checking the file size of the local disk of the production server, but when there are many servers, it is difficult to ensure that the SQL Server database is stored on each server. path is the same. Through the above embodiments, the database information stored on a plurality of distributed deployment servers can be obtained.

As an optional embodiment, as shown in FIG. 3 , after acquiring database information on one or more servers deployed in a distributed manner, the above method may further include the following steps:

Step S302, obtaining identification information of one or more servers deployed in a distributed manner;

Step S304, the identification information and the database information on the server are stored in the database temporary table.

Specifically, in the above steps, the above-mentioned server may be one or more servers deployed in a distributed manner; the above-mentioned identification information may be an IP address used to identify each server in the distributed deployment; After the database information on each server, a temporary table can be established in the database to store the obtained database information on different servers, and the identification information of the corresponding server can be obtained and stored in the temporary table to distinguish which server the database comes from. .

Optionally, the database information on different servers in the same domain can be obtained sequentially by using the Windows identity.

Through the above-mentioned embodiment, a temporary database table is established for summarizing and recording database information obtained from multiple servers deployed in a distributed manner, so as to achieve the purpose of batch analysis of databases on different servers.

In an optional embodiment, as shown in FIG. 4 , in the above step S104, the database to be rebuilt is determined according to the size of the file stored in the database and/or the total number of rows in the table, which may include the following steps:

Step S402, judging whether the database satisfies a preset condition, wherein the preset condition includes at least any one of the following: the size of the file stored in the database is greater than a preset threshold, and the total number of rows of the table stored in the database is greater than the preset number of rows;

Step S404: Screen out the database that meets the preset condition from the database temporary table.

Specifically, in the above-mentioned steps, the above-mentioned database may be a database deployed on one or more servers in a distributed manner; the above-mentioned preset condition may be any condition preset for processing the database. In an optional example, the above-mentioned The preset condition may be the size of the file stored in the database, and/or the total number of rows of the table stored in the database, according to the size of the file stored in the database on one or more servers deployed in a distributed manner and the total number of rows of the table, It is judged whether the database in the database temporary table satisfies the preset condition, and the database that satisfies the preset condition in the database temporary table is filtered and screened, so as to obtain the database that needs to be rebuilt.

In a preferred embodiment, the above preset conditions are simultaneously satisfied that the size of the file stored in the database is greater than a preset threshold, and the total number of rows of the table stored in the database is greater than the preset number of rows.

Through the above embodiments, the purpose of screening all databases that need to be rebuilt among the databases on one or more servers deployed in a distributed manner can be achieved.

In an optional embodiment, as shown in FIG. 5 , the rebuilding of the database to be rebuilt in the foregoing step S106 may include the following steps:

Step S502, obtaining the database that needs to be rebuilt in the database temporary table;

Step S504, delete the database that needs to be rebuilt;

Step S506, using the template database to rebuild the database that needs to be rebuilt.

Specifically, in the above steps, after filtering out the database that needs to be rebuilt in the temporary table of the database according to the size of the file stored in the database and/or the total number of rows in the data table, delete the database that needs to be rebuilt, use the blank, no A template database of any data rebuilds the database that needs to be rebuilt.

Optionally, based on the foregoing embodiment, before deleting the database that needs to be rebuilt, the foregoing method further includes: backing up the database that needs to be rebuilt to a local disk or a backup server.

In an optional embodiment, as shown in FIG. 6, after using the template database to rebuild the database to be rebuilt, the above method may further include the following steps:

Step S602, verifying the reconstructed database;

Step S604, in the case that the verification is successful, delete the database backed up in the local disk or the backup server.

As a preferred embodiment, the above-mentioned embodiment of the present application can be described with reference to the flowchart of the method for batch rebuilding data in SQL Server shown in FIG. 7 . As shown in FIG. 7 , the method includes the following steps:

Step S702, using SQL to query database information on different servers.

In the above-mentioned steps, the above-mentioned database information may include: the size of the files stored in the database and the total number of rows in the table, and by executing the database system table, the database files, log files, and tables of the databases on multiple servers of distributed deployment can be obtained. details such as the number of rows.

In an optional embodiment, the following program can be used to query database information on different servers. Program example:

Select name, convert(float, size)*(8192.0/1024.0)/1024/1024.FromWebDissectorReceiver_800003.

Select Count(*)Number of table rows

FROM[WebDissectorReceiver_800003].[E_Session].

The output of the above program is:

table row count 456153

As can be seen from the above output results, the database name obtained by the query is WebDissectorReceiver, the size of the database file is 1.12890625, and the total number of rows in the table in the database is 456153.

Step S704: Store the acquired database information in a new data table, and add a character string to record the IP address of the server during storage.

In the above steps, the information of all databases on all servers in the entire production environment can be stored in a new database table by using a loop statement, and a string field is added to record the IP address of the server during storage.

In an optional embodiment, the following program can be used to realize storing the acquired database information in a new data table. Some program examples:

The output is:

ID Dbname mdf ldf TableCount Server 0 receiver 1.128906 0.29937 23456 172.1.1.1

In the above embodiment, Dbname represents the data name, mdf represents the database file, ldf represents the log file, TableCount represents the number of table rows in the database, and Server represents the server. It can be seen from the above output results that after storing the receiver database to a new data table, in the new data table, the table ID number of the database is 0, the name of the database is receiver, the size of the database file is 1.128906, and the log The file size is 0.29937, the number of rows in the table is 23456, and the IP address of the server where the database is located is 172.1.1.1.

Step S706, back up the database to a local disk or a cold standby server.

In the above steps, the database on one or more servers deployed in a distributed manner is backed up to a local disk or a backup server (for example, a cold standby server).

In an optional embodiment, the batch backup of databases on multiple servers can be implemented by the following code, and some program examples are:

In an optional embodiment, the above script code is copied to the GWD target database server SQL Server Management Studio, the execution parameters are changed according to the actual situation, the DEBUG mode is used to check whether the script output in Messages is correct, and @ExecMode is changed after confirming that it is correct.

It should be noted here that the batch backup database does not include the AS library. The AS library can be created based on the template in the j:d method of the AS program, so backup is not required.

Preferably, the above-mentioned backup server may be a cold backup server.

Step S708: Determine the database to be rebuilt according to the size of the file stored in the database and the total number of rows in the table.

In the above steps, after the acquired database information is stored in a new data table, the database to be rebuilt is determined according to the size of the file stored in the database and the total number of rows in the table.

Step S710, delete the old database.

In the above steps, after determining the databases that need to be rebuilt, delete these databases on multiple servers deployed in a distributed manner.

Step S712, create a new database.

In the above steps, after the databases on the multiple servers deployed in a distributed manner are deleted, new databases are created on these servers by using the template data.

Step S714, delete the backup database after verification.

The solutions disclosed in the above embodiments of the present application do not use the window local disk to obtain the size of the disk file occupied by the database, but instead use the system table of the database in SQL Server to obtain the size of the occupied disk file, which is accurate and easy to import into the database table, Moreover, it is convenient to use SQL statement filter conditions for filtering. After the filtering is successful, the script is deleted and then rebuilt uniformly, so as to avoid inconsistent file paths of different servers caused by the sql-server deployment path.

Example 2

According to an embodiment of the present invention, an embodiment of an apparatus for batch rebuilding a database is also provided. The method for batch rebuilding a database in Embodiment 1 of the present invention may be executed in the apparatus of Embodiment 2 of the present invention.

FIG. 8 is a schematic diagram of an apparatus for batch rebuilding a database according to an embodiment of the present invention. As shown in FIG. 8 , the apparatus includes: an acquisition module 801 , a determination module 803 , and a creation module 805 .

Wherein, the obtaining module 801 is used to obtain database information on one or more servers of distributed deployment, wherein the database information at least includes: the name of the database, the size of the file stored in the database, the total row of the data table stored in the database The determining module 803 is used for determining the database that needs to be rebuilt according to the size of the file and/or the total number of rows in the data table; the creating module 805 is used for rebuilding the database that needs to be rebuilt.

It can be seen from the above that in the above-mentioned embodiment of the present application, by obtaining the file size and the number of rows of the table stored in the databases on different servers in the same domain, and according to the two indicators of the size of the file and the number of rows of the table stored in the database to determine the database that needs to be rebuilt, and finally rebuild the database that needs to be rebuilt based on the template data. It is easy to note that the solutions disclosed in the above-mentioned embodiments of the present application do not use this disk to obtain the file size of the disk space occupied by the database, but obtain database information on multiple different servers from the database management system. The size and the number of rows in the table are analyzed to determine the database that needs to be rebuilt, so as to achieve the purpose of batch processing the databases on one or more servers deployed in a distributed manner, thereby realizing the batch reconstruction of databases on different servers. The technical effect further solves the technical problem that the existing technology cannot realize the batch reconstruction of the databases on multiple servers deployed in a distributed manner.

In an optional embodiment, the above-mentioned first obtaining module includes: a calling module for calling a database system table on the server through a database management system; and a second obtaining module for obtaining database information from the database system table.

In an optional embodiment, the above-mentioned apparatus further includes: a third obtaining module, configured to obtain the identification information of the server; and a storage module, configured to store the identification information and the database information of the server in a temporary database table.

In an optional embodiment, the above determination module further includes: judging whether the database satisfies a preset condition, wherein the preset condition includes any one of the following: the size of the file is greater than a preset threshold, and the total number of rows in the data table is greater than a preset Set the number of rows; filter out the database that meets the preset conditions from the database temporary table.

In an optional embodiment, the above-mentioned creation module further includes: a fourth acquisition module, used for acquiring the database that needs to be rebuilt in the temporary table of the database; a first deletion module, used for deleting the original data in the database that needs to be rebuilt ; The processing module is used to rebuild the database that needs to be rebuilt by using the template data.

In an optional embodiment, the above-mentioned apparatus further includes: a second storage module, configured to back up the original data stored in the database that needs to be rebuilt to a local disk or a backup server.

In an optional embodiment, the above-mentioned apparatus further includes: a verification module for verifying the reconstructed database; a second deletion module for deleting the local disk or the backup server when the verification is successful database backed up in .

The above-mentioned serial numbers of the embodiments of the present invention are only for description, and do not represent the advantages or disadvantages of the embodiments.

In the above-mentioned embodiments of the present invention, the description of each embodiment has its own emphasis. For parts that are not described in detail in a certain embodiment, reference may be made to related descriptions of other embodiments.

In the several embodiments provided in this application, it should be understood that the disclosed technical content can be implemented in other ways. The device embodiments described above are only illustrative, for example, the division of the units may be a logical function division, and there may be other division methods in actual implementation, for example, multiple units or components may be combined or Integration into another system, or some features can be ignored, or not implemented. On the other hand, the shown or discussed mutual coupling or direct coupling or communication connection may be through some interfaces, indirect coupling or communication connection of units or modules, and may be in electrical or other forms.

The units described as separate components may or may not be physically separated, and components shown as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution in this embodiment.

In addition, each functional unit in each embodiment of the present invention may be integrated into one processing unit, or each unit may exist physically alone, or two or more units may be integrated into one unit. The above-mentioned integrated units may be implemented in the form of hardware, or may be implemented in the form of software functional units.

The integrated unit, if implemented in the form of a software functional unit and sold or used as an independent product, may be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention is essentially or the part that contributes to the prior art, or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium , including several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present invention. The aforementioned storage medium includes: U disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), mobile hard disk, magnetic disk or optical disk and other media that can store program codes .

The above are only the preferred embodiments of the present invention. It should be pointed out that for those skilled in the art, without departing from the principles of the present invention, several improvements and modifications can be made. It should be regarded as the protection scope of the present invention.

Claims (6)

1. A method for batch database reconstruction, comprising:

obtaining database information on one or more servers in a distributed deployment, wherein the database information at least comprises: the name of the database, the size of the file stored in the database, and the total number of rows of the table stored in the database;

determining a database to be reconstructed according to the size of the file stored in the database and/or the total row number of the table;

reconstructing the database to be reconstructed;

the acquiring database information on one or more servers deployed in a distributed manner includes:

calling a database system table on the server through a database management system;

acquiring the database information from the database system table;

wherein after obtaining database information on one or more servers of a distributed deployment, the method further comprises:

acquiring identification information of one or more servers deployed in a distributed manner;

and storing the identification information and the database information on the server into a database temporary table, wherein the database temporary table is established for summarizing and recording the database information on the server.

2. The method of claim 1, wherein determining the database that needs to be reconstructed based on the size of the file stored in the database and/or the total number of rows in the table comprises:

judging whether the database meets preset conditions or not, wherein the preset conditions at least comprise any one of the following conditions: the size of the file stored in the database is larger than a preset threshold value, and the total row number of the table stored in the database is larger than a preset row number;

and screening out the database meeting the preset conditions from the temporary database table.

3. The method of claim 1, wherein rebuilding the database to be rebuilt comprises:

acquiring a database to be reconstructed in the database temporary table;

deleting the database to be reconstructed;

and rebuilding the database to be rebuilt by utilizing the template database.

4. The method of claim 3, wherein prior to deleting the database requiring reconstruction, the method comprises: and backing up the database to be rebuilt to a local disk or a backup server.

5. The method of claim 4, wherein after the rebuilding the database to be rebuilt using the template database, the method further comprises:

checking the reconstructed database;

and deleting the database backed up in the local disk or the backup server under the condition of successful verification.

6. An apparatus for batch reconstruction of a database, comprising:

a first obtaining module, configured to obtain database information on one or more servers in distributed deployment, where the database information at least includes: the name of the database, the size of a file stored in the database, and the total number of rows of a data table stored in the database;

the determining module is used for determining the database to be reconstructed according to the size of the file stored in the database and/or the total row number of the table;

the creating module is used for reconstructing the database needing to be reconstructed;

wherein the first obtaining module comprises:

the calling module is used for calling the database system table on the server through a database management system;

the second acquisition module is used for acquiring the database information from the database system table;

wherein the apparatus further comprises:

the third acquisition module is used for acquiring the identification information of the server;

and the first storage module is used for storing the identification information and the database information on the server into a database temporary table, wherein the database temporary table is established and used for summarizing and recording the database information on the server.

Images